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: add clusterResourcePlacement and components doc #598

Merged
merged 2 commits into from
Nov 9, 2023

Conversation

zhiying-lin
Copy link
Contributor

Description of your changes

add doc

Fixes #

I have:

  • Run make reviewable to ensure this PR is ready for review.

How has this code been tested

Special notes for your reviewer

@zhiying-lin zhiying-lin changed the title doc: add clusterResourcePlacement and components doc docs: add clusterResourcePlacement and components doc Nov 7, 2023
@zhiying-lin zhiying-lin merged commit d6474f7 into Azure:main Nov 9, 2023
5 checks passed
@zhiying-lin zhiying-lin deleted the arch branch November 9, 2023 02:16
Comment on lines +166 to +184
Conditions:
Last Transition Time: 2023-11-06T10:22:56Z
Message: found all the clusters needed as specified by the scheduling policy
Observed Generation: 2
Reason: SchedulingPolicyFulfilled
Status: True
Type: ClusterResourcePlacementScheduled
Last Transition Time: 2023-11-06T10:22:56Z
Message: All 2 cluster(s) are synchronized to the latest resources on the hub cluster
Observed Generation: 2
Reason: SynchronizeSucceeded
Status: True
Type: ClusterResourcePlacementSynchronized
Last Transition Time: 2023-11-06T10:22:56Z
Message: Successfully applied resources to 2 member clusters
Observed Generation: 2
Reason: ApplySucceeded
Status: True
Type: ClusterResourcePlacementApplied
Copy link
Contributor

Choose a reason for hiding this comment

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

can we use an example that the last transition time is different ?

Comment on lines +133 to +142
## Rollout Strategy
Update strategy determines how changes to the `ClusterWorkloadPlacement` will be rolled out across member clusters.
The only supported update strategy is `RollingUpdate` and it replaces the old placed resource using rolling update, i.e.
gradually create the new one while replace the old ones.

## Placement status

After a `ClusterResourcePlacement` is created, details on current status can be seen by performing a `kubectl describe crp <name>`.
The status output will indicate both placement conditions and individual placement statuses on each member cluster that was selected.
The list of resources that are selected for placement will also be included in the describe output.
Copy link
Contributor

Choose a reason for hiding this comment

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

can we add links to the deep dive "how to" section of the doc here after they are done?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants