-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Add log level for kube components patch to ClusterClass #9493
🌱 Add log level for kube components patch to ClusterClass #9493
Conversation
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.
/area e2e-testing
@nawazkh @kubernetes-sigs/cluster-api-release-team
/test |
@killianmuldoon: The
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
/test pull-cluster-api-e2e-full-dualstack-and-ipv6-main |
test/e2e/data/infrastructure-docker/main/clusterclass-quick-start.yaml
Outdated
Show resolved
Hide resolved
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.
/lgtm
LGTM label has been added. Git tree hash: bf926fb99a46ca66bc23bad02b9a1319d91a4691
|
I'll merge this once I've taken a look at the output logs in the dualstack tests where it's enabled. |
/lgtm |
test/e2e/data/infrastructure-docker/main/clusterclass-quick-start.yaml
Outdated
Show resolved
Hide resolved
870074c
to
8ecfb97
Compare
/test pull-cluster-api-e2e-full-dualstack-and-ipv6-main |
test/e2e/data/infrastructure-docker/main/clusterclass-quick-start.yaml
Outdated
Show resolved
Hide resolved
8ecfb97
to
94eb7d9
Compare
/test pull-cluster-api-e2e-full-dualstack-and-ipv6-main |
94eb7d9
to
5f9b40a
Compare
/test pull-cluster-api-e2e-full-dualstack-and-ipv6-main |
Updated this so there's two variables - one for the kube control plane and another for kubelets. I think that's broken down enough for our needs - kubelet doesn't tend to log much in our tests as we don't schedule many pods. Log level 4 is way too high for the api server and the controller-manager though. I looked at the |
Looks in working order now - the output with the higher log levels is here |
- name: kubeControlPlaneLogLevel | ||
schema: | ||
openAPIV3Schema: | ||
type: string | ||
description: "Log level for kube-apiserver, kube-scheduler and kube-controller-manager" | ||
default: "0" | ||
- name: kubeletLogLevel | ||
schema: | ||
openAPIV3Schema: | ||
type: string | ||
description: "Log level for kubelets on control plane and worker nodes" | ||
default: "0" |
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.
NIT!
- name: kubeControlPlaneLogLevel | |
schema: | |
openAPIV3Schema: | |
type: string | |
description: "Log level for kube-apiserver, kube-scheduler and kube-controller-manager" | |
default: "0" | |
- name: kubeletLogLevel | |
schema: | |
openAPIV3Schema: | |
type: string | |
description: "Log level for kubelets on control plane and worker nodes" | |
default: "0" | |
- name: kubeControlPlaneLogLevel | |
schema: | |
openAPIV3Schema: | |
type: string | |
description: "Log level for kube-apiserver, kube-scheduler and kube-controller-manager" | |
default: "" | |
- name: kubeletLogLevel | |
schema: | |
openAPIV3Schema: | |
type: string | |
description: "Log level for kubelets on control plane and worker nodes" | |
default: "" |
I'd suggest to default to empty string and not patch if the value is empty string (enabledIf
). This way we would always keep the default. (may require to split the patch with regards to the variables)
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.
Good idea!
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.
Should be done now
ccf8a93
to
a43f40b
Compare
I'll also have to cherry-pick this back to v1.5 manually so we get coverage there for the flakes in the test. Can't auto-cherry-pick because of the MachinePool stuff. |
a43f40b
to
82ceecc
Compare
/retest |
I verified this locally - but I can add PR-Blocking to the test if you want to be sure it works. Just don't want to have to run the full dualstack suite again to see some log lines 😅 |
82ceecc
to
5a64c88
Compare
/hold For CI run with blocking on the dualstack test. |
test/e2e/data/infrastructure-docker/main/clusterclass-quick-start.yaml
Outdated
Show resolved
Hide resolved
test/e2e/data/infrastructure-docker/v1.5/clusterclass-quick-start.yaml
Outdated
Show resolved
Hide resolved
Going to revert the PR-Blocking change: Logs from the run are here if you'd like to compare: https://gcsweb.k8s.io/gcs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api/9493/pull-cluster-api-e2e-main/1706665816436510720/artifacts/clusters/ |
5a64c88
to
5bdd5b5
Compare
Signed-off-by: killianmuldoon <kmuldoon@vmware.com>
5bdd5b5
to
c6e270e
Compare
/hold cancel |
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.
/lgtm
LGTM label has been added. Git tree hash: e424ec3c5e608f0abdee5c3b3df1ee3fb21ed586
|
Thanks for the help with this one @chrischdi! /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: killianmuldoon 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 |
Adds svariables and matching patches to set log levels for topology based clusters in e2e. The motivation for adding this is to help debug #8816.
The patch is enabled for that test in this PR, but this seems like a generally useful flag for helping debug e2e tests.