Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while using with kustomize: "mapping key "observedGeneration" already defined" #8466

Closed
kiranmenon opened this issue Feb 15, 2025 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@kiranmenon
Copy link

Getting error while trying apply eventing core using kustomize tool : mapping key "observedGeneration" already defined

I usually use kustomize (kubectl -k option) to install knative-eventing, so that I can use my custom container image repo as well can patch knative's k8s manifest files. While it was working fine till 1.15.4, for version v1.16.3, I see the error as below:

error: map[string]interface {}(nil): yaml: unmarshal errors: line 128: mapping key "observedGeneration" already defined at line 97

Expected behavior

  • Should be able to use kustomize to install knative eventing components

To Reproduce

resources:  
  - eventing-core.yaml
images:
  - name: gcr.io/knative-releases/knative.dev/eventing/cmd/controller
    newName: myrepo:8080/knative-eventing/controller
    digest: sha256:1947ff229a3afd39aefd5c58b8c2e05317d6b94bd2f0ea8e560667b261ec934b 

Knative release version
1.16.3

@kiranmenon kiranmenon added the kind/bug Categorizes issue or PR as related to a bug. label Feb 15, 2025
@kiranmenon
Copy link
Author

kiranmenon commented Feb 15, 2025

just trying to check the diff between previous versions, I commented out these lines on 3222 and that error is not there.

3222        observedGeneration:
3223                   description: ObservedGeneration is the 'Generation' of the Service that was last processed by the controller.
3224                   type: integer
3225                   format: int64

@pierDipi
Copy link
Member

pierDipi commented Feb 18, 2025

The fix was merged a while ago #8423, however, the bot is failing to release new 1.16 patch releases https://prow.knative.dev/?job=release_eventing_release-1.16_periodic

Let's see if the productivity WG knows https://cloud-native.slack.com/archives/C04LY4M2G49/p1739881045838999

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants