Comments (7)
Some discussion points from recent arch call:
1q) Operators should do more to detect conditions and present the information
1a.1) Operators do present some of that information today, but how accessible is it to the end user? For engineers looking at a CI run, that information is embedded in a large json file, and nobody really looks at it.
1a.2) For the machine-api specifically, our operator status is not tied to the status of individual machines as they are user tuneable. Often times, there's no reason to look at machine objects as they are not a primary indication (eg, etcd is down to 2/3 replicas would be the alarm) and it takes some effort to work through the layers of the stack and see a machine is having a problem and might be the root cause (or might point you to a different root cause).
2q) This information should integrate with insights/mustgather/run it in the cluster
2a) I don't disagree, that would be nice follow-on work. We can prove it in the CI as it will be most useful there immediately (we're diagnosing failed clusters)
3q) Operators should be able to self correct known conditions
3a) If etcd wants to deploy 3 replicas but can't because we don't have enough control plane hosts, it's powerless to do anything to correct that. If the machine-api can't create a new control plane host because the machineset is misconfigured or the AZ went dark, there's nothing we can do to correct that.
from enhancements.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from enhancements.
/remove-lifecycle stale
from enhancements.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from enhancements.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
/remove-lifecycle stale
from enhancements.
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
from enhancements.
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen
.
Mark the issue as fresh by commenting/remove-lifecycle rotten
.
Exclude this issue from closing again by commenting/lifecycle frozen
./close
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.
from enhancements.
Related Issues (20)
- need okd4.x hello-world example and suppport webui HOT 4
- Integration with 5G network (MEC-like functionality) HOT 4
- Geo redundancy feasible distance & solutions HOT 4
- [RFE] Operators Health Metric HOT 16
- SSO logout redirect uri new spec HOT 6
- [RFE] Sidecar container specification in the Secondary Scheduler Operator HOT 4
- Add the ability to install via dnf in fedora HOT 4
- vSphere IPI Zonal - Streched Clusters HOT 12
- `make lint` doesnt work HOT 4
- API counts HOT 5
- Openshift-installer support for IBM Cloud HOT 5
- template-lint.sh can't handle committed file renames HOT 10
- arm64 installer files for OKD4 HOT 4
- Enhancement necessary for resource pool support on vSphere? HOT 5
- Improve markdown linter; Optimize for human time vs brittle manual markdown formatting. HOT 4
- Default tls termination configuration for user-created routes HOT 4
- OKD machineset with "Highly Available" option in oVirt HOT 5
- Support for SOCA AWS MachinePools to support EC2 Spot Best practices HOT 4
- Support or information on more cluster configurations HOT 4
- Allow Users To List Own Groups HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from enhancements.