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

Add custom image with all required packages for init containers #13900

Merged
merged 15 commits into from
Jul 22, 2019

Conversation

mshaposhnik
Copy link
Contributor

What does this PR do?

Adds custom image with all required packages for init containers to avoid problems with their installation during their execution.

What issues does this PR fix or reference?

#13870

Release Notes

N/A

Docs PR

N/A

@benoitf
Copy link
Contributor

benoitf commented Jul 18, 2019

@vparfonov FYI it will require a new setup on build-all-images-nightly CI job

@skabashnyuk
Copy link
Contributor

@monaka can you take a look too

@shaijain
Copy link

when we can expect new image to be available ?
eclipse/che-endpoint-watcher:nightly

@benoitf
Copy link
Contributor

benoitf commented Jul 19, 2019

@vparfonov ?

@mshaposhnik
Copy link
Contributor Author

Suddenly everything stopped working. There is a tons of errors. Bash not found in image anymore. Errors in entrypoint script:

 waiting for postgres to be ready...
>{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {
    
  },
  "status": "Failure",
  "message": "endpoints \"keycloak\" is forbidden: User \"system:anonymous\" cannot get resource \"endpoints\" in API group \"\" in the namespace \"che\"",
  "reason": "Forbidden",
  "details": {
    "name": "keycloak",
    "kind": "endpoints"
  },
  "code": 403
}<
/entrypoint.sh: line 26: length": command not found
jq: error: syntax error, unexpected $end, expecting QQSTRING_TEXT or QQSTRING_INTERP_START or QQSTRING_END (Unix shell quoting issues?) at <top-level>, line 1:
".subsets[]?.addresses 
jq: 1 compile error 

@benoitf
Copy link
Contributor

benoitf commented Jul 19, 2019

is it related to set -e

@mshaposhnik
Copy link
Contributor Author

I don't know. I have reverted the curl and jq lines to their prevoius state, and it's not working neither.

@mshaposhnik
Copy link
Contributor Author

Why did it gives me 403 when requesting endpoint? Is something changed recently ?

@mshaposhnik
Copy link
Contributor Author

mshaposhnik commented Jul 19, 2019

Ok the problem seems solved, if K8S doesn't fool me again using cached images instead of new ones.
image

@mshaposhnik mshaposhnik merged commit 9484d98 into master Jul 22, 2019
@mshaposhnik mshaposhnik deleted the init_image branch July 22, 2019 07:10
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