Comments (5)
This isn't really the correct repo to be discussing the helm chart, it isn't generated from here or available from here. I'd suggest creating an issue in github.com/projectcalico/calico as that is the source of the helm chart.
Sorry about that. I raised the issue here because the Helm Chart is about the tigera-operator
and I didn't find any other repository dedicated to it.
That being said, what is helm's take on charts that should have a single deployment in a cluster? In the helm docs you linked to it is referring to deploying multiple of the same chart which does not make sense with Calico. It seems better to me that it should be hard coded so there is no chance of deploying multiple of the chart, or maybe there is a better way to enforce that with helm charts.
I agree with @stevehipwell, where Helm is not focused on ensuring singleton. There are many other Helm Charts out there with the same requirement but without hard-coding namespace into the templates (AWS Load Balancer Controller, Metrics-Server, Custer Auto-Scaler, etc).
from operator.
@davivcgarcia see #1427 for a discussion on this behaviour.
The latest version of my tigera-operator chart should support being installed into any namespace as well as setting other standard values that are missing from the official chart (FYI there is currently no OpenShift support).
from operator.
This isn't really the correct repo to be discussing the helm chart, it isn't generated from here or available from here. I'd suggest creating an issue in github.com/projectcalico/calico as that is the source of the helm chart.
That being said, what is helm's take on charts that should have a single deployment in a cluster? In the helm docs you linked to it is referring to deploying multiple of the same chart which does not make sense with Calico. It seems better to me that it should be hard coded so there is no chance of deploying multiple of the chart, or maybe there is a better way to enforce that with helm charts.
from operator.
@tmjd blocking multiple installs isn't a Helm concern or feature, but I suspect that it could be achieved without needing to hardcode the operator namespace by installing an object into the kube-system
namespace that couldn't be "adopted" by further attempted installations. Off the top of my head a configmap with a fixed name being installed into kube-system
with the release namespace as a label would block additional installs.
from operator.
I'm closing this issue and opened a new on the the repository referred by @tmjd. Thanks!
from operator.
Related Issues (20)
- s390x: Build operator s390x binary and image
- BGPFilters is forbidden in version 1.30 HOT 2
- operator bundle contains 404 link to docs
- Add ability to start calico when kubeadm cluster does not have podSubnet configured HOT 5
- Support configuration of securityContext on calico installations HOT 1
- Blocking traffic to other service like to RDS, from LB in AWS HOT 2
- Duplicate FELIX_HEALTHPORT environment variable causing problems in Openshift HOT 3
- When unninstall HOT 3
- timescale for v3.10.0 update
- Installation CRD not getting status updated HOT 1
- document procedure to completely uninstall calico and operator from cluster HOT 1
- Feature request: ability to disable pod-security labels added by tigera/operator HOT 11
- Fargate anti-affinity doesn't get applied to DaemonSets HOT 1
- feature request: calico-apiserver PodDisruptionBudget HOT 2
- Operator deletes tigera-system namespace on ApiServer deployment HOT 7
- Incorrect PodCIDR in installations.operator.tigera.io ipPools prevented upgrade HOT 2
- AutoDiscoverProvider leads to wrong result
- Error running cluster on M1 / ARM Mac OS for local development HOT 13
- Calico Operator should support running different dataplanes on different nodes in the same Kubernetes cluster HOT 2
- v1.31.1 showing HIGH vulnerability CVE-2023-44487 HOT 1
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 operator.