ingressclass.kubernetes.io/is-default-class: "true" does not work

[matti]

$ kubectl get ingressclass nginx -o yaml
apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:
  annotations:
    ingressclass.kubernetes.io/is-default-class: "true"
    meta.helm.sh/release-name: ingress-nginx
    meta.helm.sh/release-namespace: default
  creationTimestamp: "2021-09-05T15:32:21Z"
  generation: 1
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/version: 1.0.0
    helm.sh/chart: ingress-nginx-4.0.1
  name: nginx
  resourceVersion: "680"
  uid: 938f1d53-6784-4007-bcdb-be112828720d
spec:
  controller: k8s.io/ingress-nginx

---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: registry
spec:
  rules:
    - host: registry.domain.com
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: registry
                port:
                  number: 80
  tls:
    - secretName: domain-tls

logs from controller:

-------------------------------------------------------------------------------
NGINX Ingress controller
  Release:       v1.0.0
  Build:         041eb167c7bfccb1d1653f194924b0c5fd885e10
  Repository:    https://github.com/kubernetes/ingress-nginx
  nginx version: nginx/1.20.1

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

W0905 15:32:49.172044       7 client_config.go:615] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0905 15:32:49.172310       7 main.go:221] "Creating API client" host="https://10.43.0.1:443"
I0905 15:32:49.179522       7 main.go:265] "Running in Kubernetes cluster" major="1" minor="21" git="v1.21.4+k3s1" state="clean" commit="3e250fdbab72d88f7e6aae57446023a0567ffc97" platform="linux/amd64"
I0905 15:32:49.753351       7 main.go:104] "SSL fake certificate created" file="/etc/ingress-controller/ssl/default-fake-certificate.pem"
I0905 15:32:49.769093       7 ssl.go:531] "loading tls certificate" path="/usr/local/certificates/cert" key="/usr/local/certificates/key"
I0905 15:32:49.779729       7 nginx.go:253] "Starting NGINX Ingress controller"
I0905 15:32:49.786515       7 event.go:282] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"default", Name:"ingress-nginx-controller", UID:"c9b57167-3510-4f87-9672-a8bf594449c3", APIVersion:"v1", ResourceVersion:"659", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap default/ingress-nginx-controller
I0905 15:32:50.886701       7 store.go:361] "Ignoring ingress because of error while validating ingress class" ingress="default/registry" error="ingress does not contain a valid IngressClass"
I0905 15:32:50.981697       7 nginx.go:295] "Starting NGINX process"

^-- see ingress does not contain a valid IngressClass

Installed with helm chart version 4.0.1 using values:

controller:
  ingressClassResource:
    default: true

[k8s-ci-robot]

@matti: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[matti]

related nginxinc/kubernetes-ingress#1221 (comment) and #7448

[rpthms]

@matti Are you setting controller.watchIngressWithoutClass to true?

ingress-nginx/charts/ingress-nginx/values.yaml

Lines 64 to 67 in 8b3a6f0

	# Process Ingress objects without ingressClass annotation/ingressClassName field
	# Overrides value for --watch-ingress-without-class flag of the controller binary
	# Defaults to false
	watchIngressWithoutClass: false

[matti]

no. thats prob it. all docs that I could find are pretty slim on this.

[longwuyuan]

Please create a doc issue Thanks, ; Long

…

On Thu, 9 Sep, 2021, 12:03 AM Matti Paksula, ***@***.***> wrote: no. thats prob it. all docs that I could find are pretty slim on this. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#7600 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGZVWSQYBQ2RMNX36NSZCLUA6T6BANCNFSM5DO5WCJQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[iusergii]

@rpthms, @longwuyuan I have multiple ingress controllers and my rules have annotation ~kubernetes.io/ingress.class: nginx... and even with watchIngressWithoutClass: true it still doesn't work.
Is there expected and is there any workaround for migration to v1?
Thanks

[longwuyuan]

/remove-kind bug
/kind support
/area documentation

Hi,

• one request is to pupulate your ingresses with the "ingressClassName" . Can you try and update results
• since you have multiple controllers, please provide details on the multiple controllers
• Does this provide any additional info to you https://kubernetes.github.io/ingress-nginx/#i-have-more-than-one-controller-running-in-my-cluster-and-i-want-to-use-the-new-spec

[k8s-ci-robot]

@longwuyuan: The label(s) area/documentation cannot be applied, because the repository doesn't have them.

In response to this:

/remove-kind bug
/kind support
/area documentation

Hi,

• one request is to pupulate your ingresses with the "ingressClassName" . Can you try and update results
• since you have multiple controllers, please provide details on the multiple controllers

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[longwuyuan]

/area docs

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.