Resorting Instance CR .md #466
Conversation
README.md
Outdated
|
|
||
| 2. Recreate the CR: | ||
|
|
||
| a) If you have a YAML definition or manifest for your CR, ensure it includes the exact name, namespace, and (if applicable) cluster ID you retrieved from the SAP BTP service instance. |
There was a problem hiding this comment.
cluster id is not configurable in the CR yaml, it is part of the deployment config.
the cluster id usally does not change (we have a code that ensures that) so i would not put this step, i would mention it only if verification step failed. (if the instance in the cluster does not have the same instance id as the BTP instance verify the cluster id matches (it is part of the context and visibile in the cockpit or btp cli), if it does not match then configure the cluster with the right id...)
There was a problem hiding this comment.
@kerenlahav pls check the new commit. Thanks
README.md
Outdated
|
|
||
| - The name of the custom resource. | ||
| - The Kubernetes namespace where the CR should reside. | ||
| - If applicable, retrieve the cluster ID or context associated with the CR in SAP BTP. This ensures the CR is recreated in the correct environment. |
There was a problem hiding this comment.
@kerenlahav I assume you are talking about removing the third one.
README.md
Outdated
| @@ -950,7 +950,37 @@ Do not call this API with the service-operator-access plan credentials. | |||
|
|
|||
| <b>Attention: **Use this option only for cleanup purposes for a cluster that's no longer available.** Applying it to an active and available cluster may result in unintended resource leftovers in your cluster.</b> | |||
|
|
|||
| ### I can see my service instance in SAP BTP, but not its corresponding custom resource in a cluster. What can I do? | |||
There was a problem hiding this comment.
I can see my service instance in SAP BTP, but not its corresponding custom resource my cluster. How can I restore it in the cluster?
There was a problem hiding this comment.
@kerenlahav I think Avi wanted a more generally-worded question, but I changed.
Pull Request Template
Prerequisites
Motivation
Describe the problem you're trying to solve or the feature you're proposing in addition to a link to the related issue.
Approach
How does this change address the problem?
Pull Request status
Feel free to construct the checklist with whatever items seem most reasonable for your change. You could disassemble the Implementation part to even smaller separate checklist items if you're working on something big for example. But do make the effort to provide a checklist of some sort so that the core team as well as the community can have an idea about the progress of your Pull Request.
Third-party code
If you use third party code with your contribution such as, components, libraries, or snippets make sure to mention that.
Work in Progress label
For as long as development of your Pull Request is still ongoing you MUST label it with a wip label as well as prefix the name of the PR with [WIP].
For example: [WIP] Service brokers API