update PE to support a new ns scoped pods field and status conditions #70
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
feature
Which issue does this PR fix:
This PR adds a new
Spec
field to support NS scoped pods andConditions
intoStatus
to support PE objects' states tracking.What does this PR do / Why do we need it:
We need them to support NA features and expose critical state changes of PE objects to customers.
If an issue # is not available please add steps to reproduce and the controller logs:
Testing done on this change:
new Spec field
conditions
Automation added to e2e:
Will this PR introduce any new dependencies?:
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
This shouldn't support downgraded PE CRD. Upgrading is supported and worked in test clusters.
Does this PR introduce any user-facing change?:
Yes. PE objects' states are exposed.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.