This repository has been archived by the owner on Nov 15, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 40
Top level name is not propagated to single service #33
Labels
Comments
same for persistentVolumes |
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jun 19, 2017
If only one root level service is defined, then the resulting Kubernetes service will have the name populated as the root level name field. The same is being done in case of root level persistent volume. Also, tests have been added for this behavior. Fixes kedgeproject#33
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jun 20, 2017
If only one root level service is defined, then the resulting Kubernetes service will have the name populated as the root level name field. The same is being done in case of root level persistent volume. Also, tests have been added for this behavior. Fixes kedgeproject#33
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jun 21, 2017
If only one root level service is defined, then the resulting Kubernetes service will have the name populated as the root level name field. The same is being done in case of root level persistent volume. Also, tests have been added for this behavior. Fixes kedgeproject#33
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jun 21, 2017
If only one root level service is defined, then the resulting Kubernetes service will have the name populated as the root level name field. The same is being done in case of root level persistent volume. Also, tests have been added for this behavior. Fixes kedgeproject#33
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jun 21, 2017
If only one root level service is defined, then the resulting Kubernetes service will have the name populated as the root level name field. The same is being done in case of root level persistent volume. Also, tests have been added for this behavior. Fixes kedgeproject#33
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jun 22, 2017
If only one root level service is defined, then the resulting Kubernetes service will have the name populated as the root level name field. The same is being done in case of root level persistent volume. Also, tests have been added for this behavior. Fixes kedgeproject#33
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
the result is invalid service:
what I expected is Service named 'test'
The text was updated successfully, but these errors were encountered: