Skip to content
This repository has been archived by the owner on Apr 28, 2022. It is now read-only.

Operator crashes when pod policy not defined #17

Closed
Marlinc opened this issue Nov 9, 2019 · 1 comment
Closed

Operator crashes when pod policy not defined #17

Marlinc opened this issue Nov 9, 2019 · 1 comment
Assignees
@Marlinc
Labels
bug Something isn't working
Milestone
1.0.0

Comments

@Marlinc
Copy link

Marlinc commented Nov 9, 2019

While testing the operator using the e2e test suite I noticed the operator is currently crashing when the pod policy hasn't been defined for a cluster. This was caused by the merge of coreos#2103.
@Marlinc Marlinc added the bug Something isn't working label Nov 9, 2019
@Marlinc Marlinc self-assigned this Nov 9, 2019
@Marlinc Marlinc added this to the 1.0.0 milestone Nov 9, 2019
@Marlinc
Copy link
Author

Marlinc commented Nov 10, 2019

Fixed in #22

@Marlinc Marlinc closed this as completed Nov 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Marlinc Marlinc

Labels
bug Something isn't working
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@Marlinc