-
Notifications
You must be signed in to change notification settings - Fork 27
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
docs: update ro docs #1037
base: main
Are you sure you want to change the base?
docs: update ro docs #1037
Conversation
To delete the `my-deployment` on the clusters with the label `env: test` selected by the clusterResourcePlacement `crp-example`, | ||
you can use the `Delete` override type. | ||
```yaml | ||
apiVersion: placement.kubernetes-fleet.io/v1alpha1 | ||
kind: ResourceOverride | ||
metadata: | ||
name: example-ro | ||
namespace: test-namespace | ||
spec: | ||
placement: | ||
name: crp-example | ||
resourceSelectors: | ||
- group: apps | ||
kind: Deployment | ||
version: v1 | ||
name: my-deployment | ||
policy: | ||
overrideRules: | ||
- clusterSelector: | ||
clusterSelectorTerms: | ||
- labelSelector: | ||
matchLabels: | ||
env: test | ||
overrideType: Delete | ||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not move this example into the Override Type section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or move the OverrideType section earlier or remove it? Ideally, the OverrideType section should be the parent of JSON Patch Override and have a delete type section. Currently, it's at the same level as JSON Patch and no corresponding Delete section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think the current logic is to give concrete examples at the very beginning of the policy section, and then go deep into each field. it should be ok?
Description of your changes
update the ro how-to docs to include new features
Fixes #
I have:
make reviewable
to ensure this PR is ready for review.How has this code been tested
Special notes for your reviewer