-
Notifications
You must be signed in to change notification settings - Fork 62
Remove metadata.name from podTemplate #138
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: master
Are you sure you want to change the base?
Conversation
makes it more in-line with a normal Kubernetes deployment example
I think I also need to update the files in Would also be nice that we test that |
Oh indeed, it seems like the hydra job does not check that. |
it used to though if I remember correctly ... did something change? :/ |
@arianvp: It did check this. I'm also surprised, and I'm looking into this. |
@arianvp: It looks like the issue is that after my changes CI only checks the versioned releases, but not the top-level default release. I'll put up a PR soon to fix that |
… based on the discussion in #138 CI wasn't checking that the `./scripts/generate.sh` script had been run, which this change fixes
… based on the discussion in #138 CI wasn't checking that the `./scripts/generate.sh` script had been run, which this change fixes
… based on the discussion in #138 CI wasn't checking that the `./scripts/generate.sh` script had been run, which this change fixes
… based on the discussion in #138 CI wasn't checking that the `./scripts/generate.sh` script had been run, which this change fixes
@arianvp: Alright, CI is fixed now to catch when things get out of sync. See the CI error on this pull request after merging in |
makes it more in-line with a normal Kubernetes deployment example. This field is even ignored by kubernetes API for PodTemplates afaik
Also
deploymentSimple
was missing aselector
which is invalid (runtime error)