Deprecated APIs called and update

General Discussions
1

Good morning,

I have a problem updating obsolete APIs. Previously I had a cluster in version 1.22 and I managed to switch it to 1.25 by migrating the pods to containerd.

Now I always get obsolete API errors and I can’t get rid of the problem

  • /apis/extensions/v1beta1/ingresses controller/v0.0.0 (linux/amd64) kubernetes/$Format/jetstack-cert-manager/v0.14.2 (clean)

  • /apis/networking.k8s.io/v1beta1/ingresses nginx-ingress-controller/v0.0.0 (linux/amd64) kubernetes/$Format

  • /apis/extensions/v1beta1/ingress nginx-ingress-controller/v0.0.0 (linux/amd64) kubernetes/$Format

My nginx-ingress-controller was in warning, I was able to restore the situation by updating its YAML but I still have the obsolete API errors I can’t find any reference to v1beta1 in any YAML. Or am I looking wrong?

I’ve read the documentation all over the place and frankly I’m a bit lost and new to Kubernetes, I could really use some help!

Do not hesitate to ask me for any information you may need to help me out of this situation.

cloudshell:~$ kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.27.3
Kustomize Version: v5.0.1
Server Version: v1.25.8-gke.1000
WARNING: version difference between client (1.27) and server (1.25) exceeds the supported minor version skew of +/-1

2

Did you update the ingress controller as well? If it’s old, it’s likely hitting those deprecated endpoints

3

yep “i think”. The controller is indeed very old. I tried to modify the YAML so that it is no longer a status warning. But maybe I did wrong. I juste replaced registry image and chart version

apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "55"
  creationTimestamp: "2019-10-16T07:49:18Z"
  generation: 55
  labels:
    app: nginx-ingress
    chart: nginx-ingress-1.8.0
    component: controller
    heritage: Tiller
    release: nginx-ingress
  name: nginx-ingress-controller
  namespace: gitlab-managed-apps
  resourceVersion: "907611062"
  uid: 75270c2c-efe9-11e9-9cda-42010a840091
spec:
  progressDeadlineSeconds: 2147483647
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: nginx-ingress
      component: controller
      release: nginx-ingress
  strategy:
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 1
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: nginx-ingress
        component: controller
        release: nginx-ingress
    spec:
      containers:
      - args:
        - /nginx-ingress-controller
        - --default-backend-service=gitlab-managed-apps/nginx-ingress-default-backend
        - --election-id=ingress-controller-leader
        - --ingress-class=nginx
        - --configmap=gitlab-managed-apps/nginx-ingress-controller
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        image: registry.k8s.io/ingress-nginx/controller:v1.8.0@sha256:744ae2afd433a395eeb13dc03d3313facba92e96ad71d9feaafc85925493fee3
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 3
          httpGet:
            path: /healthz
            port: 10254
            scheme: HTTP
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: nginx-ingress-controller
        ports:
        - containerPort: 80
          name: http
          protocol: TCP
        - containerPort: 443
          name: https
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /healthz
            port: 10254
            scheme: HTTP
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        resources: {}
        securityContext:
          allowPrivilegeEscalation: true
          capabilities:
            add:
            - NET_BIND_SERVICE
            drop:
            - ALL
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      serviceAccount: nginx-ingress
      serviceAccountName: nginx-ingress
      terminationGracePeriodSeconds: 60
status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: "2019-10-16T07:49:18Z"
    lastUpdateTime: "2019-10-16T07:49:18Z"
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  observedGeneration: 55
  readyReplicas: 1
  replicas: 1
  updatedReplicas: 1