-
Notifications
You must be signed in to change notification settings - Fork 769
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
specifying service type right now is very docker-compose specific #273
Comments
+1. I think that makes sense. |
surajssd
added a commit
to surajssd/kompose
that referenced
this issue
Nov 9, 2016
Moved label handling code from Transformer to loader, to make it generic to handle creating service types. Added new attribute to ServiceConfig which gets populated in loader. Fixes kubernetes#273
surajssd
added a commit
to surajssd/kompose
that referenced
this issue
Nov 16, 2016
Moved label handling code from Transformer to loader, to make it generic to handle creating service types. Added new attribute to ServiceConfig which gets populated in loader. Fixes kubernetes#273
procrypt
pushed a commit
to procrypt/kompose
that referenced
this issue
Nov 25, 2016
Moved label handling code from Transformer to loader, to make it generic to handle creating service types. Added new attribute to ServiceConfig which gets populated in loader. Fixes kubernetes#273
procrypt
pushed a commit
to procrypt/kompose
that referenced
this issue
Nov 25, 2016
Moved label handling code from Transformer to loader, to make it generic to handle creating service types. Added new attribute to ServiceConfig which gets populated in loader. Fixes kubernetes#273
procrypt
pushed a commit
to procrypt/kompose
that referenced
this issue
Dec 5, 2016
Moved label handling code from Transformer to loader, to make it generic to handle creating service types. Added new attribute to ServiceConfig which gets populated in loader. Fixes kubernetes#273
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use
labels
from docker-compose to specify type of service (e.g.kompose.service.type: nodeport
) that gets created and this gets mapped toannotatations
internally but then we can do this cleanly by adding one more directive inServiceConfig
namedServiceType string
so that at loader stage itself we load this variable and in transformation we don't need to do annotation checking!So basically now we add one vairable to
ServiceConfig
and move code fromCreateService
to respective loaders.The text was updated successfully, but these errors were encountered: