Upgrade issue from 2.6 to 2.7

htgurukul commented 3 months ago

Describe the bug Upgrading ALB controller on EKS 1.28 from version 2.6 to 2.7 below error is thrown

root@ubuntu-xenial:/vagrant/clus_upgrade/to_1.29# kubectl apply -f v2_7_0_full.yaml customresourcedefinition.apiextensions.k8s.io/ingressclassparams.elbv2.k8s.aws configured customresourcedefinition.apiextensions.k8s.io/targetgroupbindings.elbv2.k8s.aws configured role.rbac.authorization.k8s.io/aws-load-balancer-controller-leader-election-role unchanged clusterrole.rbac.authorization.k8s.io/aws-load-balancer-controller-role configured rolebinding.rbac.authorization.k8s.io/aws-load-balancer-controller-leader-election-rolebinding unchanged clusterrolebinding.rbac.authorization.k8s.io/aws-load-balancer-controller-rolebinding unchanged service/aws-load-balancer-webhook-service unchanged deployment.apps/aws-load-balancer-controller unchanged certificate.cert-manager.io/aws-load-balancer-serving-cert unchanged issuer.cert-manager.io/aws-load-balancer-selfsigned-issuer unchanged unable to decode "v2_7_0_full.yaml": parsing time "null" as "2006-01-02T15:04:05Z07:00": cannot parse "null" as "2006" unable to decode "v2_7_0_full.yaml": parsing time "null" as "2006-01-02T15:04:05Z07:00": cannot parse "null" as "2006"

Steps to reproduce kubectl apply -f v2_7_0_full.yaml Expected outcome command should not return any error and manifest should be applied to cluster.

Environment

AWS Load Balancer controller version 2.6 to 2.7
Kubernetes version 1.28
Using EKS (yes/no), if so version? Yes 1.28 Additional Context: NA

htgurukul commented 3 months ago

Any update???

htgurukul commented 3 months ago

I did resolve it. replaced "null" with null in manifest.and it worked. I hope it have no impact.

k8s-triage-robot commented 3 days ago

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

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

/lifecycle stale

kubernetes-sigs / aws-load-balancer-controller

Upgrade issue from 2.6 to 2.7 #3658