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.

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: pause docs on repo #1518

Merged

Conversation

acpana
Copy link
Collaborator

@acpana acpana commented Apr 5, 2024

Pause docs for the repo.

cc @ziyue-101

Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>
Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>

To pause KCC across namespaces it is suffcient to set the ConfigConnector's `actuationMode: Paused`. This will work when KCC runs in `Cluster` and `Namesapced` mode. To eventually resume actuation just set the field back to `Reconciling`.

### Pausing Per Namespace
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is worth mentioning that the Pause field on ConfigConnectorContext takes precedence of ConfigConnector.

@@ -0,0 +1,43 @@
# Pause KCC

> `Feature State`: KCC version v1.114+ (alpha)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have a better suggestion, but this was a little hard to read. Maybe "alpha as of version v1.114" ? We could also ask taryn :-)

We extended the API definitions for the ConfigConnector and ConfigConnectorContext resources to
support a new field, `spec.actuationMode`. The field's current supported values are `Reconciling`
and `Paused` with `Reconciling` being the default for backwards compatiblity.
As such, KCC can be "paused" both globablly and on a per namespace level if running in namesapce mode
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in globally. And probably per-namespace (with a hyphen). Also typo in namespace :-)


### Pausing Globally

To pause KCC across namespaces it is suffcient to set the ConfigConnector's `actuationMode: Paused`. This will work when KCC runs in `Cluster` and `Namesapced` mode. To eventually resume actuation just set the field back to `Reconciling`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe search for "amesap". You're not the only one to make this typo :-)

reconciling can be turned on for a namespace by changing the `actuationMode`
field for the`ConfigConnectorContext` to `Reconciling` for that namespace.
NOTE: you can avoid any pausing in actuation by first changing the
`ConfigConnectorContext` actuationMode first.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: you say "first" twice


### Eventual state transitions & Jitter

When changing actuation modes for a cluster or namespace, a KCC resource should eventually actuate
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe "When you un-pause actuation, reconciliation will not happen immediately, but will instead start happening on the normal re-reconciliation interval (with jitter). We may enhance this behaviour in future"

@justinsb
Copy link
Collaborator

Looks pretty good to me, a few nits, and maybe we should get our professional writers to look at it? One way to do that is to make the equivalent change in our "cloud.google.com" docs. I suggest starting with copy-and-paste reuse this time, but thinking about how we can share content easily going forwards.

docs/features/pause.md Outdated Show resolved Hide resolved
docs/features/pause.md Outdated Show resolved Hide resolved
docs/features/pause.md Outdated Show resolved Hide resolved
docs/features/pause.md Outdated Show resolved Hide resolved
docs/features/pause.md Outdated Show resolved Hide resolved
docs/features/pause.md Outdated Show resolved Hide resolved

It can be handy to have KCC globally paused but reconciling on a per
namespace level. To do this make sure KCC is running in `Namespaced` mode
and the `actuationMode: Paused` on the `ConfigConnector` resource. Then
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: probably "is set on" instead of "on" (?)

@justinsb
Copy link
Collaborator

LGTM ... one phrasing nit but not blocking

/approve
/lgtm

Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justinsb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow google-oss-prow bot merged commit a140bdf into GoogleCloudPlatform:master May 21, 2024
3 checks passed
yuwenma pushed a commit to yuwenma/k8s-config-connector that referenced this pull request Jun 1, 2024
* docs: add feature docs

Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>

* docs: also link from release notes

Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>

* Apply suggestions from code review

---------

Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>
anhdle-sso pushed a commit to anhdle-sso/k8s-config-connector that referenced this pull request Jun 6, 2024
* docs: add feature docs

Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>

* docs: also link from release notes

Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>

* Apply suggestions from code review

---------

Signed-off-by: Alex Pana <8968914+acpana@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants