Comments (9)
phoracek
commented on July 23, 2024
1
I guess we will eventually need to make HCO more flexible, but to start with something radical: We should stay opinionated and strict about the "right" way to deploy the cluster. Ideally, none of underlying operators' attributes should be exposed. The only exception would be a scenario where there is no sane default (name of host network devices that should be exposed) or it is based on attribute of the cluster that is unknown to us (e.g. if there are no SR-IOV NICs available, we don't want to enable SR-IOV plugins).
Could we start making a list of (existing and planned) attributes for each operator? Maybe a Google document would be a better place to discuss that.
from hyperconverged-cluster-operator.
booxter
commented on July 23, 2024
@phoracek even more radical, I don't see a problem to start SR-IOV device plugin with no devices, and to copy SR-IOV CNI plugin to a directory even if there is nothing to manage on a particular node.
from hyperconverged-cluster-operator.
kubevirt-bot
commented on July 23, 2024
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
from hyperconverged-cluster-operator.
rthallisey
commented on July 23, 2024
/remove-lifecycle stale
from hyperconverged-cluster-operator.
kubevirt-bot
commented on July 23, 2024
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
from hyperconverged-cluster-operator.
kubevirt-bot
commented on July 23, 2024
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
from hyperconverged-cluster-operator.
kubevirt-bot
commented on July 23, 2024
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
from hyperconverged-cluster-operator.
kubevirt-bot
commented on July 23, 2024
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
from hyperconverged-cluster-operator.
kubevirt-bot
commented on July 23, 2024
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten./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 hyperconverged-cluster-operator.
Related Issues (20)
- [build] HOT 4
- When using TLS13 it should not be allowed to specify any ciphers HOT 1
- Dependency Dashboard
- Dependency Dashboard
- Dependency Dashboard
- Dependency Dashboard
- Dependency Dashboard HOT 1
- Action Required: Fix Renovate Configuration
- Can't deploy hyper-converged using the deploy/deploy.sh script
- Fix issue in deploy/deploy.sh
- Installing the latest kubevirt hyperconverged via OLM throws a nil pointer exception HOT 4
- v1.10.0 image pull errors HOT 4
- [release-1.10] Backport CDI 1.58.0 into 1.10 operator release HOT 2
- Getting cert errors HOT 1
- Support emulation configuration on HyperConverged CRD HOT 1
- Dependency Dashboard HOT 1
- ImagePullBackOff for hco-operator and hco-webhook HOT 4
- Please opt-out platform-engineering-bot user. The renovate team uses a different bot user.
- Web Console and CLI installation not the same HOT 1
- Service "cdi-api" not found when trying to create a data-volume; operator installation possibly broken HOT 5
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 hyperconverged-cluster-operator.