-
Notifications
You must be signed in to change notification settings - Fork 21
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
Keycloak uses DeploymentConfig rather than Deployment #28
Comments
Spoke with @dimitraz about this and asked her to open the issue |
It looks like the keycloak-apb always used a Openshift
Support for the kubernetes style deployment seems to be still in Tech Preview: https://docs.openshift.org/latest/dev_guide/deployments/kubernetes_deployments.html I'd be in favor of supporting both, Openshift and Kubernetes but it looks like at this point we can't use |
Your right about keycloak actually. I think in actual fact what has changed in fh-sync-server perhaps? But aside from that: I Hadn't noticed it was only tech preview for openshift. But I still think we should support both. Perhaps the broker could pass in the platform target, if it doesn't already and we can choose which template to use based on this. |
ping @david-martin |
@maleck13 The ASB does support Kubernetes and i've asked the guys if there's a way for a playbook to know if it's running in Openshift or Kubernetes. Looks like there is: https://github.com/ansibleplaybookbundle/postgresql-apb/blob/master/playbooks/provision.yaml#L5 The broker changes the value of this variable to either "openshift" or "kubernetes". So in Ansible we could possibly query '{{ cluster }}' and depending on the value use |
Reaching out to see when it could be out of tech preview openshift/openshift-docs#5254 (comment). Having the APB support both dc's and deployments is a bit of overhead. Not just in the APB, but the mobile cli too. |
@pb82 Does this make sense to you? Which would you prefer as an apb developer, that we just use deployments or that we maintain 2 sets of objects and switch based on the target. My choice would be to just use Deployments and get some kind of answer to when it is expected out of tech preview. |
I like that thinking. to be able address the full k8s user space |
@dimitraz loop me in for a potential PR - happy to review/test ;-) |
@maleck13 Yes i think we should just use Deployments if that's ok. Maintaining two different configurations would make apb development very difficult. |
Ok guys so it sounds like we are in agreement on using deployments for our services. Will you guys update the service backlogs with an issue to do this? |
I'd think let's create a JIRA and move it to the backlog, no ?
…On Mon, Jan 29, 2018 at 11:06 AM, Craig Brookes ***@***.***> wrote:
Ok guys so it sounds like we are in agreement on using deployments for our
services. Will you guys update the service backlogs with an issue to do
this?
@pb82 <https://github.com/pb82> @matzew <https://github.com/matzew>
@david-martin <https://github.com/david-martin>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJnzpFHDUA70xnWD9_4Yl4Nicp2wCbxks5tPZgugaJpZM4RuKke>
.
--
Matthias Wessendorf
github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
|
@matzew yes thats what I meant ? Maybe some confusion :) |
It looks like a recent changed has caused Keycloak to use a deployment config rather than a deployment which means we can't deploy it to kubernetes. This also has a knock-on effect on the CLI as we expect a deployment
Should we be supporting both Kubernetes and Openshift using a deployment rather?
@matzew @maleck13 @pb82
The text was updated successfully, but these errors were encountered: