My Personal Ngoprek Problems >_

[k8s] OKD Virtualization Automate VMs with Tekton Pipelines - part 3

2023-12-13T00:00:00+07:00

OKD Virtualization and Tekton Pipelines

Let’s continue demonstrating the automation of virtual machines with Tekton pipelines. I’ll provide step-by-step instructions in a video so you can follow the details of each step easily.

Ubuntu VMs

Windows VMs

Reference

OKD Docs

[k8s] OKD Virtualization Automate VMs with Tekton Pipelines - part 2

2023-12-11T00:00:00+07:00

OKD Virtualization and Tekton Pipelines

Let’s continue discussing OKD Virtualization. Now, I’ll show you how we can automate the setup and customization of VMs in OKD Virtualization using Tekton Pipelines.

Tekton Pipeline

Tekton is an open-source cloud-native Continuous Integration and Continuous Delivery/Deployment (CI/CD) solution. It simplifies deployments across various platforms by abstracting the underlying implementation details.

Tekton introduces several standard Custom Resource Definitions (CRDs) for defining CI/CD pipelines that can be used across different Kubernetes distributions.

How Tekton Works?

Task: It defines a set of build steps, such as compiling code, running tests, and building and deploying images.
Pipeline: It defines the set of tasks that make up a pipeline.
PipelineResource: It defines an object that serves as an input (e.g., a Git repository) or an output (e.g., a Docker image) of the pipeline.
PipelineRun: It instantiates a Pipeline for execution with specific inputs, outputs, and execution parameters.

Kubevirt Tekton tasks

KubeVirt Tekton tasks offer specific Tekton tasks designed for OpenShift Virtualization. These tasks primarily focus on:

Creating, updating, and managing KubeVirt resources (such as VMs, DataVolumes, DataSources, and Templates).
Performing operations on disk images using libguestfs tools.

List of Kubevirt Tekton tasks:

Create Virtual Machines
- create-vm-from-manifest - create VM from yaml manifest
- create-vm-from-template - create VM from template
Utilize Templates
- copy-template - copy template
- modify-vm-template - update template metadata
Create DataVolumes/DataSources
- create-datavolume-from-manifest (4.11) - create dataVolume
- modify-data-object (>= 4.12) - create/delete dataVolume/dataSource
Generate SSH Keys
- generate-ssh-keys - generate SSH keys and store them in cluster
Execute Commands in Virtual Machines
- execute-in-vm: execute commands over SSH
- cleanup-vm: execute commands and/or stop/delete VMs
Manipulate PVCs with libguestfs tools
- disk-virt-customize: execute virt-customize commands in PVCs
- disk-virt-sysprep: execute virt-sysprep commands in PVCs
Wait for Virtual Machine Instance Status
- wait-for-vmi-status - wait for VM status

https://github.com/kubevirt/kubevirt-tekton-tasks

Setup Tekton Tasks Operator

install tekton operator

$ export TEKTON_VERSION=v0.65.1
$ oc apply -f  "https://github.com/tektoncd/operator/releases/download
/${TEKTON_VERSION}/openshift-release.yaml"

enable tekton task from okd hco

$ oc patch hco kubevirt-hyperconverged -n kubevirt-hyperconverged --type=merge -p '{"spec":{"featureGates":{"deployTektonTaskResources":true}}}'

Create Tekton Pipelines

source: https://github.com/ammarun11/kubevirt-tekton-pipelines

We’ll create pipelines for Ubuntu VMs and Windows VMs Go to terminal or oc/kubectl client,

oc create ns openinfra2023
oc project openinfra2023

# Ubuntu VM piplines
oc create -f https://raw.githubusercontent.com/ammarun11/kubevirt-tekton-pipelines/main/examples/pipelines/okd/server-deployer-flask/server-deployer-flask-ubuntu.yaml

# Windows VM pipelines
## Need Create ConfigMap unattend & sysprep for automate deployment for windows image

oc create -f https://raw.githubusercontent.com/ammarun11/kubevirt-tekton-pipelines/main/examples/pipelines/okd/windows10/windows10-customize-sysprep.yaml
oc create -f https://raw.githubusercontent.com/ammarun11/kubevirt-tekton-pipelines/main/examples/pipelines/okd/windows10/windows10-template-autounattend.yaml

# Windows VM Template
oc create -f https://raw.githubusercontent.com/ammarun11/kubevirt-tekton-pipelines/main/examples/pipelines/okd/windows10/windows10-template.yaml
# Windows VM Customize
oc create -f https://raw.githubusercontent.com/ammarun11/kubevirt-tekton-pipelines/main/examples/pipelines/okd/windows10/windows10-customize.yaml

Results,

For creating VMs will be on next part,

Next Part 3

Reference

OKD Docs

[k8s] Setup OKD Virtualization and launch VMs - part 1

2023-12-07T00:00:00+07:00

OKD

let’s talk about OKD in a simple way. Think of it as a cool platform for building and running apps in containers. Whether you’re dealing with just a handful of machines or a massive data center, OKD has your back. It’s built on top of Kubernetes, the powerhouse behind stuff like streaming, ecommerce, holding, gaming, and online banking.

The best part? You can use it with Red Hat’s open technologies to take your apps beyond one cloud – use ‘em on your own servers or in different cloud setups. Flexibility at its finest!”

here is for the layer

OKD Virtualization

Now we break down OKD Virtualization. It’s like an extra feature or add-on for OKD that lets you handle both virtual machines (VMs) and containers together.

With OKD Virtualization, you get new tools in your OKD cluster, thanks to Kubernetes magic. Here’s what you can do:

Create and take care of Linux and Windows virtual machines.
Run pod and VM tasks side by side in your cluster.
Connect to your VMs using different tools and consoles.
Bring in existing VMs or make copies of them.
Handle stuff like network controllers and storage disks for your VMs.
Move your VMs around between nodes easily.

Plus, there’s a slick web console to help you manage all these virtual goodies right alongside your OKD containers. It plays nicely with Red Hat OpenShift Data Foundation features too!”

Alright, let’s next talk about engine behind it. The hyperconverged-cluster-operator (Kubevirt), or HCO for short, is like a control center for various other operators in Kubernetes, such as kubevirt, cdi, and networking. It’s kind of like an operator for operators – a one-stop-shop for deploying and configuring them.

HCO doesn’t replace or mess with OLM (Operator Lifecycle Manager). Instead, it helps you create operator Custom Resources (CRs) as you see fit.

So, let’s dive into how you can use HCO through a Custom Resource Definition (CRD) method. It’s a straightforward way to make the most of this feature. Let’s roll!”

Here for the OKD Virtulization Architecture

kubevirt

HCO

Requirements,

A few requirements need to be met before you can begin:

You’ll need an OKD cluster or something like OpenShift, you can follow this guide to deploy okd simple way Code Ready Openshift/OKD or other deployment guide Deploy Openshift
Don’t forget to have the kubectl/oc client utility ready to roll.

Deploy KubeVirt HyperConverged Cluster Operator from the OperatorHub

Go to OperatorHub > Search KubeVirt > and select Kubevirt hyco cluster operator

Create CR to trigger HCO

After few minutes..

ok now we create vm with okd virtualization

first create namespace for our workspace vms and go to catalog oh look we’ve catalog VMs with datasource(datavolume) ready it, so now we can run vms more easy ~

DataSource/DataVolume objects are custom resources that are provided by the Containerized Data Importer (CDI) project. Data volumes orchestrate import, clone, and upload operations that are associated with an underlying persistent volume claim (PVC). Data volumes are integrated with OKD/OpenShift Virtualization, and they prevent a virtual machine from being started before the PVC has been prepared.

oc create ns ammarun

# switch project/namespace

oc projects ammarun

Go to dashboard Select Fedora catalog > then fill the things here

you can customize spesification of vms, storage etc

after reviewing, CreateVirtualmachine

On the storage side

And here our nice VM is ready to goo ~

Next Part 2

Reference

OKD Docs

[Ceph] Setup Microceph RadosGW

2023-07-25T00:00:00+07:00

Brief

All native protocols on Microceph (RBD, CephFS and RGW) are supported, Once you have your Ceph Object Storage service up and running, you may administer the service with user management, access controls, quotas and usage tracking among other features.

Enable RadosGW Microceph

microceph enable rgw

microceph status
---output
MicroCeph deployment summary:
- am-ceph1 (10.20.14.68)
  Services: mds, mgr, mon, rgw, osd
  Disks: 3
- am-ceph2 (10.20.14.69)
  Services: mds, mgr, mon, osd
  Disks: 3
- am-ceph3 (10.20.14.70)
  Services: mds, mgr, mon, osd
  Disks: 3

ceph -s
---output
  cluster:
    id:     a7bdc86e-5cce-4697-96cc-c4b29a5a50e2
    health: HEALTH_OK

  services:
    mon: 3 daemons, quorum am-ceph1,am-ceph2,am-ceph3 (age 28h)
    mgr: am-ceph1(active, since 18h), standbys: am-ceph2, am-ceph3
    osd: 9 osds: 9 up (since 26h), 9 in (since 28h)
    rgw: 1 daemon active (1 hosts, 1 zones)

  data:
    pools:   12 pools, 305 pgs
    objects: 4.56k objects, 23 GiB
    usage:   67 GiB used, 113 GiB / 180 GiB avail
    pgs:     305 active+clean

Create RadosGW access user

microceph.radosgw-admin key create --uid=test --key-type=s3 --access-key fooAksesKunci --secret-key fooKunciRahasia

---output
{
    "user_id": "test",
    "display_name": "testuser",
    "email": "",
    "suspended": 0,
    "max_buckets": 1000,
    "subusers": [],
    "keys": [
        {
            "user": "test",
            "access_key": "fooAksesKunci",
            "secret_key": "fooKunciRahasia"
        }
    ],
    "swift_keys": [],
    "caps": [],
    "op_mask": "read, write, delete",
    "default_placement": "",
    "default_storage_class": "",
    "placement_tags": [],
    "bucket_quota": {
        "enabled": false,
        "check_on_raw": false,
        "max_size": -1,
        "max_size_kb": 0,
        "max_objects": -1
    },
    "user_quota": {
        "enabled": false,
        "check_on_raw": false,
        "max_size": -1,
        "max_size_kb": 0,
        "max_objects": -1
    },
    "temp_url_keys": [],
    "type": "rgw",
    "mfa_ids": []
}

Install awscli

apt install -y awscli

List user and zone

radosgw-admin user list
radosgw-admin zone list

Configure aws client user

aws configure --profile=test
---
AWS Access Key ID [None]: fooAksesKunci
AWS Secret Access Key [None]: fooKunciRahasia
Default region name [None]: default
Default output format [None]: json

Create bucket

aws --profile test --endpoint-url http://am-ceph1.internal.ammarun.id s3api create-bucket --bucket bucket0

aws --profile test --endpoint-url http://am-ceph1.internal.ammarun.id s3 ls
---output
2023-07-25 16:25:22 bucket0

radosgw-admin bucket list
--output
[
    "bucket0"
]

create sample object then upload to bucket

for a in {1..20}
do
  fallocate -l 100M isiember$a
  aws --profile test --endpoint-url http://am-ceph1.internal.ammarun.id s3 cp isiember$a s3://bucket0
done

List object in bucket

aws --profile test --endpoint-url http://am-ceph1.internal.ammarun.id s3 ls s3://bucket0
---output
2023-07-25 16:36:25  104857600 isiember1
2023-07-25 16:36:46  104857600 isiember10
2023-07-25 16:36:47  104857600 isiember11
2023-07-25 16:36:49  104857600 isiember12
2023-07-25 16:36:51  104857600 isiember13
2023-07-25 16:36:52  104857600 isiember14
2023-07-25 16:36:55  104857600 isiember15
2023-07-25 16:36:57  104857600 isiember16
2023-07-25 16:36:58  104857600 isiember17
2023-07-25 16:37:00  104857600 isiember18
2023-07-25 16:37:02  104857600 isiember19
2023-07-25 16:36:28  104857600 isiember2
2023-07-25 16:37:04  104857600 isiember20
2023-07-25 16:36:30  104857600 isiember3
2023-07-25 16:36:32  104857600 isiember4
2023-07-25 16:36:34  104857600 isiember5
2023-07-25 16:36:36  104857600 isiember6
2023-07-25 16:36:38  104857600 isiember7
2023-07-25 16:36:40  104857600 isiember8
2023-07-25 16:36:42  104857600 isiember9

[Ceph] Setup Ceph cluster with Microceph

2023-07-24T00:00:00+07:00

Brief

MicroCeph is a lightweight way of deploying a Ceph cluster using just a few commands, resulting in reliable and resilient distributed storage. MicroCeph is aimed at small scale private-clouds.

we’re here used ceph quincy version

Check out MicroCeph’s documentation at https://canonical-microceph.readthedocs-hosted.com/en/latest/.

Nodes

- am-ceph1 (OSD Disk: vdb,vdc,vdd) 
- am-ceph2 (OSD Disk: vdb,vdc,vdd)
- am-ceph3 (OSD Disk: vdb,vdc,vdd)

Initial Setup

To get started install the MicroCeph snap with the following command on each node to be used in the cluster:

snap install microceph --channel=quincy/stable && snap refresh --hold microceph

Connect the microceph snap to the hardware-observe and block-devices so disks on os will knew by snap package interface:

snap connect microceph:hardware-observe
snap connect microceph:block-devices

Then bootstrap init the cluster from the first node:

ssh am-ceph1
microceph init
Please choose the address MicroCeph will be listening on [default=10.20.10.68]: 10.20.14.68
Would you like to create a new MicroCeph cluster? (yes/no) [default=no]: yes
Would you like to add additional machines to the cluster? [default=empty]: am-ceph2
eyJuYW1lIjoiYW0tY2VwaDIiLCJzZWNyZXQiOiJjNjhmODllMTE2MTIyMWFmNzQ3MTlhNzQ3MDYyY2RiYWEzZmFkYTdkNjhkMTljY2E1ZmE1MDI3NTkxM2QyZGI2IiwiZmluZ2VycHJpbnQiOiI4OGMzNzFhNDJlMGY3MDIxZTgyYThhM2RlZjJiZDQxMDFiODQwYmRhNGM3YWYwOTQ0NTBiZjc0OTMzM2QzMWVmIiwiam9pbl9hZGRyZXNzZXMiOlsiMTAuMjAuMTAuNjg6NzQ0MyJdfQ==
# move to am-ceph2
Would you like to add additional machines to the cluster? [default=empty]: am-ceph3
eyJuYW1lIjoiYW0tY2VwaDIiLCJzZWNyZXQiOiJjMjcyMTU2M2Y4YTVhYTRiOWJlYzM5MTMxZmJiMzY1ZWIzN2MyNzJiNzJhZmI2MTQ2NjBlN2M1ZGQ0Y2U0ZTc2IiwiZmluZ2VycHJpbnQiOiI4OGMzNzFhNDJlMGY3MDIxZTgyYThhM2RlZjJiZDQxMDFiODQwYmRhNGM3YWYwOTQ0NTBiZjc0OTMzM2QzMWVmIiwiam9pbl9hZGRyZXNzZXMiOlsiMTAuMjAuMTAuNzA6NzQ0MyIsIjEwLjIwLjEwLjY4Ojc0NDMiXX0
# move to am-ceph3
# skip enter path disk
Show local disks available, option to directly enter path ? [default=empty]: 

ssh am-ceph2
microceph init
Please choose the address MicroCeph will be listening on [default=10.20.10.69]: 10.20.14.69
Would you like to create a new MicroCeph cluster? (yes/no) [default=no]: no
Please enter your join token: eyJuYW1lIjoiYW0tY2VwaDIiLCJzZWNyZXQiOiJjNjhmODllMTE2MTIyMWFmNzQ3MTlhNzQ3MDYyY2RiYWEzZmFkYTdkNjhkMTljY2E1ZmE1MDI3NTkxM2QyZGI2IiwiZmluZ2VycHJpbnQiOiI4OGMzNzFhNDJlMGY3MDIxZTgyYThhM2RlZjJiZDQxMDFiODQwYmRhNGM3YWYwOTQ0NTBiZjc0OTMzM2QzMWVmIiwiam9pbl9hZGRyZXNzZXMiOlsiMTAuMjAuMTAuNjg6NzQ0MyJdfQ==
# skip enter path disk
Show local disks available, option to directly enter path ? [default=empty]: 

ssh am-ceph3
microceph init
Please choose the address MicroCeph will be listening on [default=10.20.10.70]: 10.20.14.70
Would you like to create a new MicroCeph cluster? (yes/no) [default=no]: no
Please enter your join token: eyJuYW1lIjoiYW0tY2VwaDIiLCJzZWNyZXQiOiJjMjcyMTU2M2Y4YTVhYTRiOWJlYzM5MTMxZmJiMzY1ZWIzN2MyNzJiNzJhZmI2MTQ2NjBlN2M1ZGQ0Y2U0ZTc2IiwiZmluZ2VycHJpbnQiOiI4OGMzNzFhNDJlMGY3MDIxZTgyYThhM2RlZjJiZDQxMDFiODQwYmRhNGM3YWYwOTQ0NTBiZjc0OTMzM2QzMWVmIiwiam9pbl9hZGRyZXNzZXMiOlsiMTAuMjAuMTAuNzA6NzQ0MyIsIjEwLjIwLjEwLjY4Ojc0NDMiXX0
# skip enter path disk
Show local disks available, option to directly enter path ? [default=empty]: 

Check the cluster status with the following command:

microceph.ceph status
or
ceph -s

Adding OSDs

Exec on all node (am-ceph1, am-ceph2, am-ceph3)

microceph disk add /dev/vdb --wipe
microceph disk add /dev/vdc --wipe
microceph disk add /dev/vdd --wipe

Check the cluster status with the following command:

# microceph.ceph status
or
# ceph -s

  cluster:
    id:     a7bdc86e-5cce-4697-96cc-c4b29a5a50e2
    health: HEALTH_OK

  services:
    mon: 3 daemons, quorum am-ceph1,am-ceph2,am-ceph3 (age 9m)
    mgr: am-ceph1(active, since 9m), standbys: am-ceph2, am-ceph3
    osd: 9 osds: 9 up (since 9m), 9 in (since 9m)

  data:
    pools:   1 pools, 1 pgs
    objects: 0 objects, 15 GiB
    usage:   1 GiB used, 180 GiB / 180 GiB avail
    pgs:     1 active+clean

Operational Ceph Block Storage

Create block device image

Create pool

ceph osd pool create pool-test1 8 
rbd pool init pool-test1
rbd create pool-test1/block0 --size 1028

check block rbd that are contained in pool-test1

rbd list pool-test1
rbd info pool-test1/block0

rbd image 'block0':
        size 1.0 GiB in 257 objects
        order 22 (4 MiB objects)
        snapshot_count: 0
        id: 3fd3bcd87005b
        block_name_prefix: rbd_data.3fd3bcd87005b
        format: 2
        features: layering, exclusive-lock, object-map, fast-diff, deep-flatten
        op_features:
        flags:
        create_timestamp: Mon Jul 24 22:32:13 2023
        access_timestamp: Mon Jul 24 22:32:13 2023
        modify_timestamp: Mon Jul 24 22:32:13 2023

Maping image to block device

ceph-mon filled by node-mon on am-ceph1

rbd map pool-test1/block0 -k /etc/ceph/ceph.client.admin.keyring
rbd showmapped

id  pool        namespace  image   snap  device
0   pool-test1             block0  -     /dev/rbd0

Format filesystem

mkfs.xfs /dev/rbd0

Mount block device

mkdir /mnt/block0
mount /dev/rbd0 /mnt/block0
df -h

Filesystem      Size  Used Avail Use% Mounted on
udev            7.9G     0  7.9G   0% /dev
tmpfs           1.6G  1.3M  1.6G   1% /run
/dev/vda1        39G  2.6G   37G   7% /
---
/dev/rbd0      1018M   40M  979M   4% /mnt/block0

[Proxmox] Preview Setup Cluster In Proxmox

2023-05-18T00:00:00+07:00

Nodes

- pve-proxmox-1
- pve-proxmox-2
- pve-proxmox-3

Prerequites

Each node (pve-proxmox-1, pve-proxmox-2, and pve-proxmox-3) has proxmox VE installed
Each node can be accessed by its GUI
Each node can be connected to each other
Each node has chrony installed

Setup

Via Dashboard

Login to one of the proxmox dashboards (pve-proxmox-1)
Click Datacenter Section -> Cluster -> Create Cluster

Enter the cluster name (cluster-prox) and select the network (172.168.1.101) to be used, and click Create

On Cluster Information, click Join Information, then click Copy Information

Login to other node proxmox dashboard (pve-proxmox-2 and pve-proxmox-3)
Click Datacenter Section -> Cluster -> Join Cluster

Paste the encoded cluster information that was copied earlier, then enter the password from the Proxmox node, click Join
Wait until the joining cluster process is complete
Verify, Enter one of the Proxmox node dashboards, Click the Datacenter Section -> Cluster

With Command-Line

Create cluster
```
pvecm create cluster-prox
```
Cek Status
```
pvecm status
```

add another nodes to cluster

# login to server another nodes
pvecm add {ip-address-node-new}
pvecm add 172.168.1.101

Verify ``` root@pve-proxmox-1:~# pvecm status Cluster information ——————- Name: cluster-prox Config Version: 3 Transport: knet Secure auth: on

Quorum information

Date: Sat Jul 16 09:16:29 2022 Quorum provider: corosync_votequorum Nodes: 3 Node ID: 0x00000001 Ring ID: 1.47 Quorate: Yes

Votequorum information

Expected votes: 3 Highest expected: 3 Total votes: 3 Quorum: 2
Flags: Quorate

Membership information

Nodeid      Votes Name 0x00000001          1 172.168.1.101 (local) 0x00000002          1 172.168.1.102 0x00000003          1 172.168.1.103 ```

[Openstack] Resize root partition in VM Openstack

2023-02-14T00:00:00+07:00

Guide Resize Mounted Volume in VM Openstack

Eventually we need to resize volume root /dev/sda, which is the root partition; the problem is root partition cannot detach, so how we can resize the size of the root partition? Here’s your answer dude

Resize From OpenStack Side

## set the status to available to a volume
openstack volume set --state available {volume id}

## resize the volume
openstack volume set --size 40 {volume id}

## check size and status again
openstack volume show {volume id}

## set status to in-use again
openstack volume set --state in-use {volume id}

Resize Volume from VM Side

## Grow part (Contoh akan resize root partisi)
sudo growpart /dev/vda 1

## Check apakah sudah grow sesuai volume baru
lsblk

## Resize ‘/’ partition to fill all space
sudo resize2fs /dev/vda1

## (option) If your filesystem is XFS, it can be grown while mounted using the xfs_growfs command:

sudo xfs_growfs /

## Verify 
sudo df -H

if no space left on the block device, running command:

$ sudo mount -o size=10M,rw,nodev,nosuid -t tmpfs tmpfs /tmp

After the process unmount /tmp

sudo umount /tmp

IF LVM Volume :

1. Refresh LVM VG (LVM from lsblk)

vgchange --refresh

2. Resize pv

pvresize /dev/sdX

3. Extend lv

lvextend -l +100%FREE /dev/<vg_name>/<lv_name>

4. Mount /dev//

mount /dev/<vg_name>/<lv_name> /mnt

5. Filesystem grow

- Jika filesystem XFS

xfs_growfs /dev/<vg_name>/<lv_name>

- Jika filesystem . . . . Lanjutkan

```

[Preview] DevOps With Gitlab CI/CD

2023-01-28T00:00:00+07:00

Preview

DevOps pipeline

Stack Technology,

Gitlab as CI/CD
Harbor
Kubernetes
Trivy Scan image

CI/CD Staging pipeline

Sample pipeline gitlab

stages:
  - build
  - scan
  - update-chart-and-code
  - deploy-stg
  - create-mr
  - prod-approval
  - deploy-prod

variables:
  IMAGE: "cx-harbor.lab.id/ammar/odoo-gitlab"
  APP_NAME_STG: "odoo-gl-stg"
  REPO_BRANCH_STG: "staging"
  APP_NAME: "odoo-gl-prod"
  REPO_BRANCH: "production"
  REPO_URL: "https://go.lab.id/ammar/odoo-source.git"
  REPO_URL_2: "https://go.lab.id/ammar/odoo-source"
  HELM_REPO: https://cx-harbor.lab.id/chartrepo/ammar

before_script:
  - docker login $HARBOR_URL -u $HARBOR_USERNAME -p $HARBOR_PASSWORD
  - docker info
  - helm repo add ammar $HELM_REPO --force-update
  - helm repo list

Build and Push Image:
  stage: build
  only:
    - staging
  script:
    - export TAG=$(git tag --list | sort -V | tail -n1)
    - echo $TAG
    - cd odoo
    - echo "Build Container Image"
    - docker build -t $IMAGE:16-latest .
    - docker tag $IMAGE:16-latest $IMAGE:16-$TAG-rc
    - docker tag $IMAGE:16-latest $IMAGE:16-$TAG
    - docker push $IMAGE:16-$TAG-rc
    - docker push $IMAGE:16-$TAG
    - docker push $IMAGE:16-latest

Scan Image:
  stage: scan
  only:
    - staging
  before_script:
    - export TAG=$(git tag --list | sort -V | tail -n1)
    - echo $TAG
  script:
    - echo "$TAG image scanned using Harbor integrated Trivy Scanner"
    - trivy image --no-progress $IMAGE:16-$TAG-rc
    # - trivy image --no-progress --exit-code 0 --severity HIGH,CRITICAL $IMAGE:16-$TAG-rc
    - sleep 5

Push Chart & Code:
  allow_failure: true
  stage: update-chart-and-code
  only:
    - staging
  before_script:
    - export TAG=$(git tag --list | sort -V | tail -n1)
    - export IMAGE_STG=cx-harbor.lab.id/ammar/odoo-gitlab:16-$TAG-rc
    - export IMAGE_PROD=cx-harbor.lab.id/ammar/odoo-gitlab:16-$TAG
    - echo $TAG
  script:
    # Git Preparation
    - git config user.email "ammar@lab.id"
    - git config user.name "ammarun11"
    - git checkout staging
    - git pull origin staging
    # --- Update Helm Chart Version ---
    - yq e -i '.version=strenv(TAG)' helm/odoo-gl/Chart.yaml
    - yq e -i '.appVersion=strenv(TAG)' helm/odoo-gl/Chart.yaml
    - cat helm/odoo-gl/Chart.yaml
    # --- Update Staging Values ---
    - yq e -i '.container.image=strenv(IMAGE_STG)' helm/odoo-gl/values.yaml
    - cat helm/odoo-gl/values.yaml
    - yq e -i '.container.image=strenv(IMAGE_STG)' helm/odoo-gl/values-stg.yaml
    - cat helm/odoo-gl/values-stg.yaml
    # --- Update Production Values ---
    - yq e -i '.container.image=strenv(IMAGE_PROD)' helm/odoo-gl/values-prod.yaml
    - cat helm/odoo-gl/values-prod.yaml
    # --- Update Environment Variable ---
    - echo VERSION=$TAG > helm/version.env
    # --- Push Chart to Harbor ---
    - helm repo add ammar $HELM_REPO --force-update
    - helm cm-push --username $HARBOR_USERNAME --password $HARBOR_PASSWORD helm/odoo-gl/ ammar
    - helm repo update
    # --- Push Code Back to Staging Branch ---
    - git add .
    - git status
    - git commit -m "Update Helm Version to $TAG"
    - git push -o ci.skip "https://ammarun11:${ACCESS_TOKEN}@go.lab.id/ammar/odoo-source.git" $REPO_BRANCH_STG

Deploy Staging:
  stage: deploy-stg
  environment: staging
  only:
    - staging
  before_script:
    - export TAG=$(git tag --list | sort -V | tail -n1)
    - echo $TAG
    - export EXIST_STG=$(helm list -n odoo-gl-stg | tail -n +2 | wc -l)
    - echo $EXIST_STG
  script:
    - git checkout staging
    - git pull origin staging
    - echo "Deploying Staging Application..."
    - if [ "$EXIST_STG" == "0" ]; then helm install $APP_NAME_STG ammar/odoo-gl --version $TAG --values helm/odoo-gl/values-stg.yaml --wait --namespace $APP_NAME_STG; else helm upgrade $APP_NAME_STG ammar/odoo-gl --version $TAG --values helm/odoo-gl/values-stg.yaml --wait --namespace $APP_NAME_STG; fi
    - helm list -n $APP_NAME_STG
    - kubectl get all -n $APP_NAME_STG

Create MR:
  before_script: []
  needs: ["Deploy Staging"]
  variables:
    GIT_STRATEGY: none
  stage: create-mr
  only:
    - staging
  script:
    - ./merge-request.sh

Approval Release:
  stage: prod-approval
  only:
    - production
  environment:
    name: production
    url: $REPO_URL
  script:
    - curl -s -X POST https://api.telegram.org/bot$TELE_TOKEN/sendMessage -d chat_id=$TELE_CHAT_ID -d parse_mode=markdown -d text="Dear Team *ammar*, Please Approve Deployment of * $APP_NAME * on Branch *production*. Please goes to $REPO_URL_2/-/environments to *Accept.*"

Deploy Production:
  needs: ["Approval Release"]
  stage: deploy-prod
  only:
    - production
  environment: 
    name: production
  when: manual
  allow_failure: false
  before_script:
    - export TAG=$(git tag --list | sort -V | tail -n1)
    - echo $TAG
    - export EXIST_PROD=$(helm list -n odoo-gl-prod | tail -n +2 | wc -l)
    - echo $EXIST_PROD
  script:
    - echo "Deploying Production Application..."
    - if [ "$EXIST_PROD" == "0" ]; then helm install $APP_NAME ammar/odoo-gl --version $TAG --values helm/odoo-gl/values-prod.yaml --wait --namespace $APP_NAME; else helm upgrade $APP_NAME ammar/odoo-gl --version $TAG --values helm/odoo-gl/values-prod.yaml --wait --namespace $APP_NAME; fi
    - helm list -n $APP_NAME
    - kubectl get all -n $APP_NAME

[Preview] Monitoring k8s with Grafana+Prometheus+Loki

2023-01-28T00:00:00+07:00

Preview

i used kube-prometheus stack

https://github.com/prometheus-operator/kube-prometheus

Grafana Dashboards

prometheus Targets

Loki

[Preview] Setup Docker instance for use with MAGEWELL CLOUD

2023-01-15T00:00:00+07:00

My Personal Ngoprek Problems >_

[k8s] OKD Virtualization Automate VMs with Tekton Pipelines - part 3

OKD Virtualization and Tekton Pipelines

Ubuntu VMs

Windows VMs

Reference

[k8s] OKD Virtualization Automate VMs with Tekton Pipelines - part 2

OKD Virtualization and Tekton Pipelines

Tekton Pipeline

How Tekton Works?

Kubevirt Tekton tasks

Setup Tekton Tasks Operator

Create Tekton Pipelines

Results,

Reference

[k8s] Setup OKD Virtualization and launch VMs - part 1

OKD

OKD Virtualization

Deploy KubeVirt HyperConverged Cluster Operator from the OperatorHub

Reference

[Ceph] Setup Microceph RadosGW

Brief

Enable RadosGW Microceph

Create RadosGW access user

Install awscli

List user and zone

Configure aws client user

Create bucket

create sample object then upload to bucket

List object in bucket

[Ceph] Setup Ceph cluster with Microceph

Brief

Nodes

Initial Setup

Then bootstrap init the cluster from the first node:

Adding OSDs

Exec on all node (am-ceph1, am-ceph2, am-ceph3)

Operational Ceph Block Storage

Create block device image

Create pool

check block rbd that are contained in pool-test1

Maping image to block device

ceph-mon filled by node-mon on am-ceph1

Format filesystem

Mount block device

[Proxmox] Preview Setup Cluster In Proxmox

Nodes

Prerequites

Setup

Via Dashboard

With Command-Line

Quorum information

Votequorum information

Membership information

[Openstack] Resize root partition in VM Openstack

Guide Resize Mounted Volume in VM Openstack

Resize From OpenStack Side

Resize Volume from VM Side

IF LVM Volume :

1. Refresh LVM VG (LVM from lsblk)

2. Resize pv

3. Extend lv

4. Mount /dev//

5. Filesystem grow

- Jika filesystem XFS

- Jika filesystem . . . . Lanjutkan

[Preview] DevOps With Gitlab CI/CD

Preview

DevOps pipeline

Stack Technology,

CI/CD Staging pipeline

Sample pipeline gitlab

[Preview] Monitoring k8s with Grafana+Prometheus+Loki

Preview

Grafana Dashboards

prometheus Targets

Loki

[Preview] Setup Docker instance for use with MAGEWELL CLOUD

Preview

Docker Setup and OS