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.

Sign up for GitHub

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

Jump to bottom

Is the "forked image" something special, or can we use the original one? #1

Open
exocode opened this issue Jun 6, 2018 · 2 comments
Open

Is the "forked image" something special, or can we use the original one? #1

exocode opened this issue Jun 6, 2018 · 2 comments

Comments

@exocode
Copy link
Owner

exocode commented Jun 6, 2018

@cornelius-keller can we use an "official image" or did you "cheated" something in your image? I could not find any insights to your image. For me it's like a blackbox...
@cornelius-keller
Copy link

Hi @exocode die now we have to use my forked image. With the original one it was not possible to use notify scripts. I created a pr in the original repo to include my changes there. See kubernetes-retired/contrib#2912 . Once this is merged we can switch back to the original k8s contrib image.

@farcaller
Copy link

Bump because the PR was merged some time ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@farcaller @exocode @cornelius-keller