-
Notifications
You must be signed in to change notification settings - Fork 615
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
CONSOLE-3243: Rename "master" to "control plane node" in node pages #11927
Conversation
/retest |
QE Approver: Docs Approver: PX Approver: Console Approver: |
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.
8 files reviewed, good.
/label px-approved |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: RickJWagner, tvu20 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/label docs-approved |
Nice work, @tvu20! Also need to include updates to Cluster Settings:
It strikes me as a little odd that we're changing "master" to "control plane", but the underlying resource labels aren't changing. So we still have "master" in the UI. For example, Screen.Recording.2022-08-05.at.10.17.35.AM.movDo we need to engage UXD here so as to avoid creating confusion for users? cc: @megan-hall |
@@ -512,7 +512,7 @@ const NodesPage = connect<{}, MapDispatchToProps>( | |||
items: [ | |||
{ | |||
id: 'master', | |||
title: t('console-app~Master'), | |||
title: t('console-app~Control plane node'), |
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.
title: t('console-app~Control plane node'), | |
title: t('console-app~Control plane'), |
@tvu20, I think this probably merits a wider discussion. Unless the resource names (e.g., /k8s/cluster/machineconfiguration.openshift.io |
@@ -297,7 +297,7 @@ export const getNotUpgradeableResources = (resources) => | |||
resources.filter((resource) => getConditionUpgradeableFalse(resource)); | |||
|
|||
export enum NodeTypes { | |||
master = 'master', |
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.
This is problematic for
export const isMCPMaster = (mcp: MachineConfigPoolKind) => mcp.metadata.name === NodeTypes.master; |
@XiyunZhao is testing on this PR |
/retest |
1 similar comment
/retest |
Hi @tvu20, based on current changes, I opened two bugs for this new feature, could you help to identify whether they need to update or not?
|
Hi @XiyunZhao, I have just pushed a new commit that addresses bug 1. I am not able to replicate the second bug on my end. |
/retest |
1 similar comment
/retest |
Addresses https://issues.redhat.com/browse/CONSOLE-3243 Changes all string occurences of "master" in the console to "control plane node".
/retest |
1 similar comment
/retest |
@tvu20: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@tvu20 sorry for bug 2, after checking, it is not a duplicate value. |
@jhadvig @XiyunZhao In our documentation, we use "control plane" with no hyphen. See the Control plane architecture docs for an example. We also have it as "control planes" no hyphen in our documentation contributor guidelines. Adding the docs-approved label as this PR looks good to me. |
/label docs-approved |
@tvu20 Is there any conclusion for this comment? Could you help to add some details to features description? |
I agree with @rhamilto. We should revisit the story since it can lead to confusion between Nodes, MachineConfig and MachineConfigPool resources, which are still using the legacy /hold |
I'm in favor of doing what we can to get away from this terminology, but I agree this will create confusion since the actual names and labels of the resources are still Have we considered fixing this at the platform level and changing the actual resource names? (I'm sure this is easier said than done since names are immutable, this is arguably API breaking, and we probably don't want to drift from upstream...) |
Poking around to see what I can find. This seems to have happened upstream via kubeadm(kubernetes/kubeadm#2200) but we won't pick those changes up in OCP as we don't leverage kubeadm. |
@sdodson has pointed out that we should at least be able to use a new node role in 4.12: https://bugzilla.redhat.com/show_bug.cgi?id=1995858 (thanks!) |
OK, here is the upstream guidance: Based on this, I'd suggest
|
Yes, we'll still need console code changes, most of which are in this PR, but we need a few tweaks based on the guidance. |
Replaced by #12209 |
Addresses https://issues.redhat.com/browse/CONSOLE-3243
Changes all string occurences of "master" in the console to "control plane node".