-
Notifications
You must be signed in to change notification settings - Fork 1
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
test issue #110
Comments
@neo-liang-sap No more than 5 labels permitted, but 21 labels were given. |
Shoot: sretestneo/sre-g-test 🟢 Last Operation
🟢 Shoot Conditions 🟢 APIServerAvailable (HealthzRequestSucceeded) 🟢 Seed Conditions 🟢 AuditlogServiceAvailability (AuditlogInstanceAttached) 🟠 Control Plane Pods Not Healthy
🟢 Worker Groups
🟢 Worker Nodes All Healthy🟢 Daemon Sets All Healthy
🟢 System Components Pods All Healthy🔴 Throttled Pods
🟠 No pod disruption budgets (PDB) defined Consequence: Workload is unprotected from voluntary disruptions such as under node rolling updates |
@neo-liang-sap You opened a priority issue on the weekend. Please read https://wiki.wdf.sap.corp/wiki/display/Kubernetes/Gardener+Support and https://wiki.wdf.sap.corp/wiki/display/Kubernetes/DevOps+24x7 carefully for more information on how Gardener is operated on a weekend. |
@gardener-robot You have mentioned internal references in the public. Please check. |
1 similar comment
@gardener-robot You have mentioned internal references in the public. Please check. |
@neo-liang-sap ℹ️ Please take note of this issue. |
@neo-liang-sap, @etiennnr This issue has not been touched since 64 days. Please add a follow up comment and/or change the |
@neo-liang-sap, @etiennnr [in-progress] This issue has not been touched since 68 days. Please add a follow up comment and/or change the |
@neo-liang-sap, @etiennnr This issue has not been touched since 70 days. Please add a follow up comment and/or change the |
@neo-liang-sap, @etiennnr This issue has not been touched since 59 work days. Please add a follow up comment and/or change the |
/handover |
@neo-liang-sap Command "/handover" failed with "AssertionError(['neo-liang-sap'])". Additional Information
|
/handover @neo-liang-sap |
@neo-liang-sap neo-liang-sap handover this issue to you, please take care. |
/handover |
@neo-liang-sap Command "/handover" failed with "AssertionError(['neo-liang-sap'])". Additional Information
|
/handover |
@neo-liang-sap Command "/handover" failed with "AssertionError((['neo-liang-sap'],))". Additional Information
|
/handover @neo-liang-sap |
@neo-liang-sap neo-liang-sap handover this issue to you, please take care. |
/handover |
@neo-liang-sap neo-liang-sap handover this ticket to you, please take care. |
/handover @neo-liang-sap |
@neo-liang-sap neo-liang-sap handover this issue to you, please take care. |
/handover |
@neo-liang-sap neo-liang-sap handover this ticket to you, please take care. |
@neo-liang-sap This issue has not been touched since 10 work days. Please add a follow up comment and/or change the |
@neo-liang-sap This issue has not been touched since 21 work days. Please add a follow up comment and/or change the |
@neo-liang-sap This issue has not been touched since 24 work days. Please add a follow up comment and/or change the |
1 similar comment
@neo-liang-sap This issue has not been touched since 24 work days. Please add a follow up comment and/or change the |
@neo-liang-sap This issue has not been touched since 28 work days. Please add a follow up comment and/or change the |
@neo-liang-sap This issue has not been touched since 92 work days. Please add a follow up comment and/or change the |
@neo-liang-sap This issue has not been touched since 97 work days. Please add a follow up comment and/or change the |
@neo-liang-sap This issue has not been touched since 174 work days. Please add a follow up comment and/or change the |
@neo-liang-sap This issue has not been touched since 293 work days. Please add a follow up comment and/or change the |
Which cluster is affected?
Cluster Details Dashboard Link
: https://dashboard.garden.dev.k8s.ondemand.com/namespace/garden-sretestneo/shoots/sre-g-test/What happened?
What you expected to happen?
When did it happen or started to happen?
Absolute
:Relative
:How would we reproduce it (concisely and precisely)?
Anything else we need to know?
Help us categorise this issue for faster resolution:
/area audit-logging auto-scaling backup certification control-plane cost delivery disaster-recovery documentation high-availability logging metering monitoring networking os performance quality security storage usability user-management
/component gardener dashboard documentation
/kind bug regression post-mortem
/os garden-linux suse-chost
/platform alicloud aws azure gcp converged-cloud
/priority critical
The text was updated successfully, but these errors were encountered: