Skip to content
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

ConfigMap in Ingress #74247

Closed
fungiboletus opened this issue Feb 19, 2019 · 4 comments
Closed

ConfigMap in Ingress #74247

fungiboletus opened this issue Feb 19, 2019 · 4 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@fungiboletus
Copy link

What would you like to be added:

I would like to deploy an Ingress with configurations settings stored inside a ConfigMap.

Proposed Solution:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  rules:
  - host:
    valueFrom:
      configMapKeyRef:
        name: ingress-config
        key: INGRESS_HOST
  - http:
      paths:
      - path:
        valueFrom:
          configMapKeyRef:
            name: ingress-config
            key: INGRESS_PATH
        backend:
          serviceName: test
          servicePort: 80

Why is this needed:

I would like to share the same configurations for my various environments (testing, stage, production,…). Today I have to manually maintain a set of files or use a template system such as Helm. It would be nice to have such a feature in Kubernetes.

This is a copy of #74201 because the discussion went off topic.

@fungiboletus fungiboletus added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 19, 2019
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 19, 2019
@fungiboletus
Copy link
Author

/sig architecture

@k8s-ci-robot k8s-ci-robot added sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 19, 2019
@neolit123
Copy link
Member

/remove-sig architecture
/sig network

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. labels Feb 19, 2019
@thockin thockin self-assigned this Mar 7, 2019
@thockin thockin added the triage/unresolved Indicates an issue that can not or will not be resolved. label Mar 8, 2019
@thockin
Copy link
Member

thockin commented Mar 21, 2019

ping to @thockin

@thockin
Copy link
Member

thockin commented Mar 22, 2019

ConfigMaps are data-plane, not control-plane. Sorry, this is unlikely to be implementable.

@thockin thockin closed this as completed Mar 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Development

No branches or pull requests

4 participants