Remove dependency on Luke his Jenkins Docker image

[MattiasGees]

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug /kind feature /kind bug

What happened: We depend on @dippynark his Jenkins docker image for setting up the Jenkins inside the Hub of tarmak.

Example where we do this. https://github.com/jetstack/tarmak/blob/master/terraform/amazon/modules/jenkins/templates/jenkins_user_data.yaml#L83

What you expected to happen: This should not depend on @dippynark and maybe even should be configurable with a parameter to let users choose their own fork of the image.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration**:
• Install tools:
• Others:

[mattbates]

@dippynark ^

[dippynark]

@mattbates we need somewhere more sensible for this to live, can you provide permissions for either Jetstack's DockerHub or quay repos so we can build it internally?

[simonswine]

These would be my suggestions:

• Migrate your github repo into jetstack/XX
• Have a mirror on our gitlab/github/XX
• Gitlab CI pushes to quay.io (which is the only valid registry for our images now)

[simonswine]

/assign @dippynark

[dippynark]

@simonswine I don't have permissions to create repos in Jetstack's GH, could you create a jenkins-tarmak repo?

[dippynark]

@mattbates @simonswine ^