stephengrider/multi-k8s

multi-k8s's Issues

Ingress service

I have also noticed that they have deprecated Ingress in the extensions/v1beta1 from kubernetes and replace with networking.k8s.io/v1beta1 and that's why my ingress-service.yaml was not working.

So here is the updated version of ingress-service.yaml as of now in year 2023.
Here is the current version of client and server of kubernetes.

{
  "clientVersion": {
    "major": "1",
    "minor": "25",
    "gitVersion": "v1.25.9",
    "gitCommit": "a1a87a0a2bcd605820920c6b0e618a8ab7d117d4",
    "gitTreeState": "clean",
    "buildDate": "2023-04-12T12:16:51Z",
    "goVersion": "go1.19.8",
    "compiler": "gc",
    "platform": "windows/amd64"
  },
  "kustomizeVersion": "v4.5.7",
  "serverVersion": {
    "major": "1",
    "minor": "26",
    "gitVersion": "v1.26.3",
    "gitCommit": "9e644106593f3f4aa98f8a84b23db5fa378900bd",
    "gitTreeState": "clean",
    "buildDate": "2023-03-15T13:33:12Z",
    "goVersion": "go1.19.7",
    "compiler": "gc",
    "platform": "linux/amd64"
  }
}

and the yaml code

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress-service
  annotations:
    kubernetes.io/ingress.class: nginx
    # rewrite means that it will rewrite the api path and send the traffic to the right resource
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  rules:
  - http:
      paths:
      - path: /
        pathType: ImplementationSpecific
        backend:
          service:
          # name should be the same as we have defined in the service
            name: client-cluster-ip-service
            port:
              number: 3000
      - path: /api/
        pathType: ImplementationSpecific
        backend:
          service:
          # name should be the same as we have defined in the service
            name: server-cluster-ip-service
            port:
              number: 5000

Regarding the deployment of postgres

I was following your course on Udemy.
I have encountered an error while creating postgres-deoployment.
When we create postgres deployment, we cannot create it with without ENV parameter and otherwiese pod stays in crashLoopBackOff status.

So here is the code which works.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: postgres-deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      component: postgres
  template:
    metadata:
      labels:
        component: postgres
    spec:
      containers:
      - name: postgres
        image: postgres
        ports:
        - containerPort: 5432
        env:
        - name: POSTGRES_HOST_AUTH_METHOD
          value: trust

You just need to add the env parameter and its values, initially to create it. But as we progress then we can change its value according to the course

Helm init ( helm lint --service-account tiller --upgrade )

helm init
This command does not exist in Helm 3, following the removal of Tiller. You no longer need to install Tiller in your cluster in order to use Helm.
while executing this command: helm lint --service-account tiller --upgrade. I got :
Error: unknown command "init" for "helm"