Skip to content
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

remove devfile and plugin registries defaults #228

Merged
merged 3 commits into from
Jul 23, 2019

Conversation

sparkoo
Copy link
Member

@sparkoo sparkoo commented Jul 19, 2019

Registries will be deployed locally by default (eclipse-che/che#13557), so we don't want to have default registries URL sent to helm.

This will now work just with helm chart. It must be synced with work on operator side.

@benoitf
Copy link
Collaborator

benoitf commented Jul 19, 2019

FYI the semantic check is failing / commit is not matching https://www.conventionalcommits.org/en/v1.0.0-beta.4/

tlsFlag = `-f ${destDir}values/tls.yaml`
}

let command = `helm upgrade --install che --force --namespace ${flags.chenamespace} --set global.ingressDomain=${flags.domain} ${setOptions} --set cheImage=${flags.cheimage} --set global.cheWorkspacesNamespace=${flags.chenamespace} --set che.workspace.devfileRegistryUrl=${flags['devfile-registry-url']} --set che.workspace.pluginRegistryUrl=${flags['plugin-registry-url']} ${multiUserFlag} ${tlsFlag} ${destDir}`
if (flags['plugin-registry-url']) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is happening if you use server:start without --plugin-registry-url ? it is failing no ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it doesn't set helm parameter so value from helm chart is used. By default registries will be deployed in your minikube and URLs will be set to those eclipse-che/che#13890

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok it was not clear enough for me that this PR can only be merged after eclipse-che/che#13890

Copy link
Member Author

@sparkoo sparkoo Jul 19, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well, I don't think that this must be merged after. Helm charts currently does not set the registry urls, but then che.properties values are used, which are again set to openshift.io ones https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che/che.properties#L580
So basically nothing happens when we merge this one. The chectl registries url params were added just 2 days ago #189

@sparkoo
Copy link
Member Author

sparkoo commented Jul 19, 2019

FYI the semantic check is failing / commit is not matching https://www.conventionalcommits.org/en/v1.0.0-beta.4/

fixed. Would be good to know this is enabled in README and not to hit it in PR. Chectl issues are in this repository or are they going to be moved to root Che repo?

@benoitf
Copy link
Collaborator

benoitf commented Jul 19, 2019

issues are in che repository.

I will update PR template and README

setOptions.push(`--set che.workspace.devfileRegistryUrl=${flags['devfile-registry-url']} --set cheDevfileRegistry.deploy=false`)
}

let command = `helm upgrade --install che --force --namespace ${flags.chenamespace} --set global.ingressDomain=${flags.domain} ${setOptions.join(' ')} --set cheImage=${flags.cheimage} --set global.cheWorkspacesNamespace=${flags.chenamespace} ${multiUserFlag} ${tlsFlag} ${destDir}`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sparkoo since you are here don't you mind pushing every --set <param> to setOptions so that the command get more readable?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep, done

Signed-off-by: Michal Vala <mvala@redhat.com>
@sparkoo
Copy link
Member Author

sparkoo commented Jul 19, 2019

@benoitf could you please approve if you are now happy with changes?

@l0rd
Copy link
Collaborator

l0rd commented Jul 19, 2019

@sparkoo you should be able to merge whenever you are happy with your PR

@l0rd
Copy link
Collaborator

l0rd commented Jul 20, 2019

I have tested it and it worked fine. The only thing is that I expected that we wait for the registries bootstrap in the Post installation checklist as we do for che, postgres and keycloak. We can add that in a separate PR as well but that would make the UX much better.

benoitf added a commit that referenced this pull request Jul 22, 2019
Reported with PR comments there: #228
benoitf added a commit that referenced this pull request Jul 22, 2019
Reported with PR comments there: #228

Change-Id: Id0ae60e226456818ff9a5421f839eeb287de4f63
Signed-off-by: Florent BENOIT <fbenoit@redhat.com>
benoitf added a commit that referenced this pull request Jul 22, 2019
Reported with PR comments there: #228

Change-Id: Id0ae60e226456818ff9a5421f839eeb287de4f63
Signed-off-by: Florent BENOIT <fbenoit@redhat.com>
benoitf added a commit that referenced this pull request Jul 22, 2019
Reported with PR comments there: #228

Change-Id: Id0ae60e226456818ff9a5421f839eeb287de4f63
Signed-off-by: Florent BENOIT <fbenoit@redhat.com>
@sparkoo
Copy link
Member Author

sparkoo commented Jul 22, 2019

I have tested it and it worked fine. The only thing is that I expected that we wait for the registries bootstrap in the Post installation checklist as we do for che, postgres and keycloak. We can add that in a separate PR as well but that would make the UX much better.

done 3ac7552

@l0rd
Copy link
Collaborator

l0rd commented Jul 22, 2019

@sparkoo thanks. One last thing: you should also stop the registries (if you find them) in the server:stop command.

Signed-off-by: Michal Vala <mvala@redhat.com>
@sparkoo
Copy link
Member Author

sparkoo commented Jul 22, 2019

yes, now, when I've changed the selectors, it does not even work

  ✖ Wait until Che pod is deleted
    → Get pods by selector "app=che" returned 3 pods (1 was expected)

I'm on it

Signed-off-by: Michal Vala <mvala@redhat.com>
@sparkoo
Copy link
Member Author

sparkoo commented Jul 22, 2019

@l0rd server:stop fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants