-
Notifications
You must be signed in to change notification settings - Fork 45
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 documentation on the list of Cluster and Service Configuration #2291
docs: add documentation on the list of Cluster and Service Configuration #2291
Conversation
Hello ebaneck,My role is to assist you with the merge of this Status report is not available. |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
|
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
bf2bede
to
944c5fa
Compare
History mismatchMerge commit #bf2bedec611f13d971853d0d90343e86444c5e68 on the integration branch It is likely due to a rebase of the branch Please use the |
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.
Overall comment:
I would get rid of the titles inside, and the introduction (does not really provide information).
I would use what's written under "Managing Cluster and Services Configurations" as the topic intro.
And then, you present the table of parameters.
It would give:
Main title
<text on managing parameters/configuration>
e990e26
to
0abe961
Compare
0abe961
to
594254f
Compare
|
||
root@bootstrap $ crictl exec -it \ | ||
$(crictl ps -q --label io.kubernetes.container.name=salt-master) bash | ||
|
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 using crictl there and not kubectl ?
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 throughout the MetalK8s documentation, we have been using crictl
to connect to the salt-master container. I think it is only fair that we stick to one for consistency
|
||
- Configuring LDAP | ||
- Configuring Active Directory(AD) | ||
|
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.
Is it something that we can do from the GUI (create user, role ...) ?
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 am afraid no for now. cc @thomasdanan
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.
@xaf-scality UI configuration is tracked with #1991
|
||
root@bootstrap $ crictl exec -it \ | ||
$(crictl ps -q --label io.kubernetes.container.name=salt-master) bash | ||
|
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.
same comment, why crictl and not kubectl ?
44d8c44
to
2165ecf
Compare
/reset |
Reset completeI have successfully deleted this pull request's integration branches. |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
|
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
/approve |
/reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: approve |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
The following options are set: approve |
Build failedThe build for commit did not succeed in branch feature/2264-provide-documentation-on-list-of-cluster-service-configuration. The following options are set: approve |
Build failedThe build for commit did not succeed in branch w/2.6/feature/2264-provide-documentation-on-list-of-cluster-service-configuration. The following options are set: approve |
Build failedThe build for commit did not succeed in branch feature/2264-provide-documentation-on-list-of-cluster-service-configuration. The following options are set: approve |
2165ecf
to
75c3632
Compare
History mismatchMerge commit #2165ecfe7d741f40500c51cbeeaf22576b03dbca on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: approve |
/reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: approve |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
The following options are set: approve |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
The following options are set: approve |
Build failedThe build for commit did not succeed in branch w/2.6/feature/2264-provide-documentation-on-list-of-cluster-service-configuration. The following options are set: approve |
75c3632
to
1a694e9
Compare
History mismatchMerge commit #75c3632fc831f0a8075079f042f95deb08e0e391 on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: approve |
This PR adds doc on the list of available Cluster and Service Configurations deployed by default in a MetalK8s cluster Closes: #2264
/reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: approve |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
The following options are set: approve |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
The following options are set: approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue None. Goodbye ebaneck. |
Component:
'docs'
Context:
See #2264
Summary:
Document the complete list of deployed cluster and service configurations
Acceptance criteria:
Closes: #2264