Support ConfigmapRef in Routes
@knobunc is already working on this.
Since Jul 12, 2017.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 4.8k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 53
Description
Our template exposes routes based on the exposed frontend URL. We are using parameters for this:
https://github.com/openshiftio/launchpad-frontend/blob/master/openshift/template.yaml#L17-L29
and
https://github.com/openshiftio/launchpad-frontend/blob/master/openshift/template.yaml#L135-L178
For everything else, we're adopting ConfigMaps, however for a homogeneous solution, @jorgemoralespou suggested that it would be really nice if we could use ConfigMapsRef in Routes too.
Version
oc v1.5.0
kubernetes v1.5.2+43a9be4
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://api.engint.openshift.com:443
openshift v3.4.1.18
kubernetes v1.4.0+776c994
Current Result
Cannot assign a ConfigMap value to the Route
Expected Result
It would be nice to allow that field to have a ConfigmapRef like the ENVs does
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.