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.

Sign up for GitHub

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

Jump to bottom

Invalid field resourceName in controller.yaml #16

Closed
Globegitter opened this issue Jun 20, 2017 · 0 comments
Closed

Invalid field resourceName in controller.yaml #16

Globegitter opened this issue Jun 20, 2017 · 0 comments

Comments

@Globegitter
Copy link

The sealed-secrets-key-admin Role has resourceName instead of resourceNames in its rules so fails on kubectl create -f controller.yaml with:

error validating "controller.yaml": error validating data: found invalid field resourceName for v1beta1.PolicyRule; if you choose to ignore these errors, turn validation off with --validate=false
@Globegitter Globegitter mentioned this issue Jun 20, 2017
Closed
anguslees added a commit to anguslees/sealed-secrets that referenced this issue Jun 21, 2017
@anguslees
Fix invalid field resourceName
62f5fcd 
`resourceName` should have been `resourceNames`.  Fixes bitnami-labs#16

(Improvements to pre-release integration testing will be done separately)
@anguslees anguslees mentioned this issue Jun 21, 2017
Merged
anguslees added a commit to anguslees/sealed-secrets that referenced this issue Jun 21, 2017
@anguslees
Fix invalid field resourceName
efef75f 
`resourceName` should have been `resourceNames`.  Fixes bitnami-labs#16

(Improvements to pre-release integration testing will be done separately)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Globegitter