-
Bug
-
Resolution: Fixed
-
Critical
-
None
Hi,
EnvFromSource definition is not parsed, I dove into the dependencies and I have seen that kubernetes [models|https://github.com/fabric8io/kubernetes-model] definitions made by fabric8 are automatically generated and in the latest release of the package EnvFrom exists in the generated schemas.
It could come from the outdated version of kubernetes [client|https://github.com/fabric8io/kubernetes-client|https://github.com/fabric8io/kubernetes-client] which is in 2.6.1 whereas the latest is in 3.0.1.
Here is an example of a deployment with env vars profided by a config map :
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: whoami
spec:
replicas: 1
template:
metadata:
labels:
app: whoami
spec:
containers:
- name: whoami
image: emilevauge/whoami
ports:
- containerPort: 80
envFrom:
- configMapRef:
name: whoami
—
apiVersion: v1
kind: ConfigMap
metadata:
name: whoami
data:
ENV_FOO: "bar"
Hope it will help !
Regards
[JENKINS-47671] EnvFromSource is not parsed
| Description |
Original:
Hi, ```EnvFromSource``` definition is not parsed, I dove into the dependencies and I have seen that kubernetes [models](https://github.com/fabric8io/kubernetes-model) definitions made by fabric8 are automatically generated and in the latest release of the package ```EnvFrom``` exists in the generated schemas. It could come from the outdated version of kubernetes [client](https://github.com/fabric8io/kubernetes-client) which is in ```2.6.1``` whereas the latest is in ```3.0.1```. Here is an example of a deployment with env vars profided by a config map : ```yaml apiVersion: extensions/v1beta1 kind: Deployment metadata: name: whoami spec: replicas: 1 template: metadata: labels: app: whoami spec: containers: - name: whoami image: emilevauge/whoami ports: - containerPort: 80 envFrom: - configMapRef: name: whoami --- apiVersion: v1 kind: ConfigMap metadata: name: whoami data: ENV_FOO: "bar" ``` Hope it will help ! Regards |
New:
Hi, *EnvFromSource* definition is not parsed, I dove into the dependencies and I have seen that kubernetes [models|[https://github.com/fabric8io/kubernetes-model]] definitions made by fabric8 are automatically generated and in the latest release of the package *EnvFrom* exists in the generated schemas. It could come from the outdated version of kubernetes [client|[https://github.com/fabric8io/kubernetes-client]|https://github.com/fabric8io/kubernetes-client] which is in *2.6.1* whereas the latest is in *3.0.1*. +Here is an example of a deployment with env vars profided by a config map :+ {code:java} apiVersion: extensions/v1beta1 kind: Deployment metadata: name: whoami spec: replicas: 1 template: metadata: labels: app: whoami spec: containers: - name: whoami image: emilevauge/whoami ports: - containerPort: 80 envFrom: - configMapRef: name: whoami — apiVersion: v1 kind: ConfigMap metadata: name: whoami data: ENV_FOO: "bar" {code} Hope it will help ! Regards |
Menghua Xiao
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
This is already addressed and fixed in https://github.com/jenkinsci/kubernetes-cd-plugin/pull/4 and available in release 0.1.4 (2017-11-07).
Sorry for the late update here.