-
Notifications
You must be signed in to change notification settings - Fork 181
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
Refactor: Remove docs which overlap with Flux website #746
Conversation
1153cf1
to
f98d079
Compare
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 do not think that this closes #664, as it is still structured in a different way than the new spec documentation around sources (e.g. "Writing a Kustomization spec" like https://github.com/fluxcd/source-controller/blob/main/docs/spec/v1beta2/buckets.md#writing-a-bucket-spec, and explicit mention of fields and their behavior).
- detects drift between the desired and state and cluster state | ||
- corrects drift by patching objects with Kubernetes server-side apply |
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.
Nit: different list style?
docs/spec/v1beta2/kustomization.md
Outdated
> Kubernetes manifests and configuration files referenced in the kustomization.yaml. | ||
> If your Git repository or S3 bucket contains only plain manifests, | ||
> then a kustomization.yaml will be automatically generated. | ||
> **Note** that if the source contains a `kustomization.yaml` file, then it should also contain |
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.
In the "new way of writing specs", I think notes have the format of:
**Note:** If the resource contains ...
opposed to putting them in a quote block.
It doesn't, I just added a ref to it. |
Ah, absolutely my bad for misreading. |
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
f98d079
to
3e935d0
Compare
Changes:
Ref: #663 #664