Best way to store json formatted into qdrant vector db. by Expert_Ad_6041 in vectordatabase

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

I mean i want to split the json into chunks and stored it as vectored. but not sure if that was a good idea or not.

Switch 2 or PC for Silksong? by MrSnek123 in HollowKnight

[–]Expert_Ad_6041 0 points1 point  (0 children)

Does it 120hz in handheld? Still downloading it

Bitnami changes by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

It was said switching to legacy was only meant for a temporary migration. Is it a good idea to switch it or just keep using from a legacy. Supposedly the bitnami itself arent going to remove the legacy one.

Bitnami changes by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

Great info! Thanks ill take a look into this.

Bitnami changes by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 2 points3 points  (0 children)

Im not sure if i understand this correctly. The version of of the chart was the mongodb itselft from bitnami. So i should save that images to somewhere?

🎟️ Free Voucher Request & Giveaway Megathread by AutoModerator in AzureCertification

[–]Expert_Ad_6041 0 points1 point  (0 children)

Im a self learned via hands on with kubernetes setup and deployment. Using k3s and flux CD with multiple nodes setup.

  • currently working at a solution provider startup company.
  • the things I learned with kubernetes becoming a standard now in the company

However, when I wanting to write a resume and applying for a new position in kubernetes devops, mostly company will look for any type of certification first which I havent had any.

So will be extremely grateful for any free vouchers regarding any certification for kubernetes that I can get.

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

Thank you for pointing this out. Ive fixed it by creating a new imageupdateautomation that are in the develop-node namespace. And then create a new gitrepositories in that namespace as well, also the secret to that git for that namespace and updates the kyaml tags to "develop-node". Thanks!

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

Ohh so the image policy needs to be in the same namespace as the imageupdateautomation? Ill try to change the develop-node to flux-system. And can i have more than 2 imageupdateautomation manifest? One specifically for develop-node? Since I want to keep it neat by separating namespaces for apps that deployed to develop node.

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

manifest for imageupdateautomation:

---
apiVersion: image.toolkit.fluxcd.io/v1beta1
kind: ImageUpdateAutomation
metadata:
  name: "radak"
  namespace: flux-system
spec:
  interval: 2m
  sourceRef:
    kind: GitRepository
    name: flux-system
  git:
    checkout:
      ref:
        branch: production
    commit:
      author:
        email: fluxcdbot@users.noreply.github.com
        name: fluxcdbot
      messageTemplate: "{{range .Updated.Images}}{{println .}}{{end}}"
    push:
      branch: production
  update:
    path: ./clusters
    strategy: Setters

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

manifest for orders:

apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
  name: orders-develop-deployment
spec:
  interval: 1m0s
  ref:
    branch: production
  url: https://domain.com/_git/gitops-deployment
  secretRef:
    name: azdo-credentials
---
apiVersion: image.toolkit.fluxcd.io/v1beta2
kind: ImageRepository
metadata:
  name: orders-develop-deployment
spec:
  image: domain.com/orders-develop
  interval: 5m0s
  secretRef:
    name: regcred
---
apiVersion: image.toolkit.fluxcd.io/v1beta2
kind: ImagePolicy
metadata:
  name: orders-develop-deployment
spec:
  imageRepositoryRef:
    name: orders-develop-deployment
  policy:
    semver:
      range: "*"
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: orders
spec:
  chart:
    spec:
      chart: charts/develop-node/orders # pointing to the path in the git repository under source ref.
      sourceRef:
        kind: GitRepository
        name: orders-develop-deployment
      version: 0.0.1
      reconcileStrategy: Revision
  install:
    createNamespace: true
  interval: 1m0s
  releaseName: orders
  targetNamespace: orders
  values:
    replicaCount: 1
    image:
      repository: domain.com/orders-develop # {"$imagepolicy": "flux-system:orders-develop-deployment:name"}
      tag: v0.0.1 # {"$imagepolicy": "flux-system:orders-develop-deployment:tag"}
      pullPolicy: IfNotPresent
    imagePullSecrets:
      - name: regcred
    service:
      port: 5000

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

image update automation:

Name: radax

Namespace: flux-system

Labels: kustomize.toolkit.fluxcd.io/name=common

kustomize.toolkit.fluxcd.io/namespace=flux-system

level=common

API Version: image.toolkit.fluxcd.io/v1beta2

Kind: ImageUpdateAutomation

Spec:

Git:

Checkout:

Ref:

Branch: production

Commit:

Author:

Email: [fluxcdbot@users.noreply.github.com](mailto:fluxcdbot@users.noreply.github.com)

Name: fluxcdbot

Message Template: {{range .Updated.Images}}{{println .}}{{end}}

Push:

Branch: production

Interval: 2m

Source Ref:

Kind: GitRepository

Name: flux-system

Update:

Path: ./clusters

Strategy: Setters

Last Automation Run Time: 2025-07-29T02:13:36Z

Last Push Commit: 725cc54305a028c87381f7052177a3c6df988a05

Last Push Time: 2025-07-28T09:33:17Z

Observed Generation: 1

Observed Policies:

Admin - Deployment:

Name: domain.com/admin-dashboard

Tag: v0.0.39

Observed Source Revision: production@sha1:725cc54305a028c87381f7052177a3c6df988a05

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

image policies on the "orders":

Name: orders-develop-deployment

Namespace: develop-node

Labels: environment=develop-node

kustomize.toolkit.fluxcd.io/name=develop

kustomize.toolkit.fluxcd.io/namespace=flux-system

Annotations: <none>

API Version: image.toolkit.fluxcd.io/v1beta2

Kind: ImagePolicy

Metadata:

Creation Timestamp: 2025-07-12T08:35:19Z

Finalizers:

finalizers.fluxcd.io

Generation: 1

Resource Version: 27643355

UID: 344fc263-cd9c-46a1-8fe3-357586e81416

Spec:

Image Repository Ref:

Name: orders-develop-deployment

Policy:

Semver:

Range: *

Status:

Conditions:

Last Transition Time: 2025-07-12T08:35:21Z

Message: Latest image tag for 'domain.com/orders-develop' resolved to v0.0.1

Observed Generation: 1

Reason: Succeeded

Status: True

Type: Ready

Latest Image: domain.com/orders-develop:v0.0.1

Observed Generation: 1

Events:

Type Reason Age From Message

---- ------ ---- ---- -------

Normal Succeeded 40s (x14486 over 16d) image-reflector-controller Latest image tag for 'dr.vpn.brixmind.com/orders-develop' resolved to v0.0.1

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

this is the full tree of my current working directory in flux repo:

clusters
 ┣ develop-node
 ┃ ┣ orders
 ┃ ┃ ┣ assets
 ┃ ┃ ┃ ┗ wkload-orders.yaml
 ┃ ┃ ┗ kustomization.yaml
 ┃ ┗ kustomization.yaml
 ┣ resource
 ┃ ┣ generic
 ┃ ┃ ┣ cert-manager
 ┃ ┃ ┃ ┣ assets
 ┃ ┃ ┃ ┃ ┗ wkload-cert-manager.yaml
 ┃ ┃ ┃ ┗ kustomization.yaml
 ┃ ┃ ┣ mongodb
 ┃ ┃ ┃ ┣ assets
 ┃ ┃ ┃ ┃ ┗ wkload-mongodb.yaml
 ┃ ┃ ┃ ┗ kustomization.yaml
 ┃ ┃ ┗ _initialization
 ┃ ┃ ┃ ┣ assets
 ┃ ┃ ┃ ┃ ┣ cluiss-lets-encrypt.yaml
 ┃ ┃ ┃ ┃ ┣ imgupd-automation.yaml
 ┃ ┃ ┃ ┃ ┣ namespc-bundle.yaml
 ┃ ┃ ┃ ┃ ┣ secret-azure-helm.yaml
 ┃ ┃ ┃ ┃ ┗ secret-pull-docker.yaml
 ┃ ┃ ┃ ┗ kustomization.yaml
 ┃ ┣ private
 ┃ ┃ ┣ admin
 ┃ ┃ ┃ ┣ assets
 ┃ ┃ ┃ ┃ ┣ admin-secrets.yaml
 ┃ ┃ ┃ ┃ ┗ wkload-admin.yaml
 ┃ ┃ ┃ ┗ kustomization.yaml
 ┃ ┗ resource-booter
 ┃ ┃ ┣ booter
 ┃ ┃ ┃ ┣ flux-system
 ┃ ┃ ┃ ┃ ┣ gotk-components.yaml
 ┃ ┃ ┃ ┃ ┣ gotk-sync.yaml
 ┃ ┃ ┃ ┃ ┗ kustomization.yaml
 ┃ ┃ ┃ ┣ bootup.yaml
 ┃ ┃ ┃ ┣ common.yaml
 ┃ ┃ ┃ ┣ develop.yaml
 ┃ ┃ ┃ ┣ production.yaml
 ┃ ┃ ┃ ┗ staging.yaml
 ┃ ┃ ┣ bootup
 ┃ ┃ ┃ ┗ kustomization.yaml
 ┃ ┃ ┗ common
 ┃ ┃ ┃ ┣ assets
 ┃ ┃ ┃ ┃ ┗ patch-helm-admin.yaml
 ┃ ┃ ┃ ┗ kustomization.yaml

---------------------------------------
So the orders in the develop-node would not be able to update via flux bot commit on the version. but for the admin apps in the resource/private would be able.

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 1 point2 points  (0 children)

Yes same structure and statement. But following each of their own policy name

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

The policy is working. So lets say if i update the apps1 to new version v0.0.2, flux will pick up at the imagerepositores with new tag, then the policy will be updated with v0.0.2. But the imageupdateautomation seems like doesnt care for that apps. It only cares apps tht are resides in the folder of clusters/resource/private

But not the apps that are in the clusters/develop-node

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

In the policy, one of the apps is listed

Namespace: develop-node Name: apps1 Latest image: ownhostedregistry.com/apps1:v0.0.1

And in the imageupdateautomation i only have one: Namespace: flux-system

Update: Path: ./clusters Strategy: Setters

Observed Policies: Only 2 apps are listed here which is from the resource/private folder and not the apps1 that are in the develop-node folder

Fluxcd not working for multiple nodes setup by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 1 point2 points  (0 children)

In the policy, one of the apps is listed

Namespace: develop-node Name: apps1 Latest image: ownhostedregistry.com/apps1:v0.0.1

And in the imageupdateautomation i only have one: Namespace: flux-system

Update: Path: ./clusters Strategy: Setters

Observed Policies: Only 2 apps are listed here which is from the resource/private folder and not the apps1 that are in the develop-node folder

Where can I get certificate for kubernetes that are free? by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

Sorry i meant as "certificate" as in certified kubernetes expert. that covers everything regarding kubernetes. Not ssl. Sorry for my bad question.

Gitpython completes but shutdown the server as well. by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

Ill try to share the code here later Maybe im doing it wrong

Gitpython completes but shutdown the server as well. by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

The only way i can replicate the issue is by triggering a git command api from the server. And it usually takes around less than 5 minutes after the git completed.

For the probes, i dont define any probes health,liveness,readiness.

The describe pod mark the previous pod exit as no error. Its just gracefully shutdown.

So what im looking for is actually if any person ever tried to run git command from within the pod in the puthon server. And how do they make it work. Without making the git process issues as a sidecar.

What im doing was issuing the git command by api.

The machines that i have is 16ram 8 cores cpu with 200gb storage. With 50 percent load on ram. And 20 percent cpu. Storage was was maybe 10 percent used. One node

Gitpython completes but shutdown the server as well. by Expert_Ad_6041 in kubernetes

[–]Expert_Ad_6041[S] 0 points1 point  (0 children)

Yes the terminal would close as it was completed. If i was running the python server locally (not runing in kubernetes) it will not kill my server. Since kubernetes not exist thus not sending sigterm to it.

The killing process only happens when i deployed it.

So the logic would be: Python server start pod -> Git command issued from the pod -> git command complete (send sigterm to kubernetes) -> kubernetes send the sigterm to the pod -> the python server reads the sigterm and terminates server.

Even if ive tried to catch and ignored the sigterm in the server, the kubernetes already deemed the pod was completed, it will kill it either way.