Skip to content

Conversation

@abhinavmpandey08
Copy link

Description

Skip downloading the cert if tinkServerTLS is not enabled

Why is this needed

New Tinkerbell stack doesn't host the cert anymore. I'm making it optional so it allows users to skip this process without breaking compatibility

Fixes: #

How Has This Been Tested?

Setup hook with tinkServerTLS to false and ensured that the cert doesn't get pulled

How are existing users impacted? What migration steps/scripts do we need?

Shouldn't affect existing users but they can set this flag explicitly to download/skip cert download

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade


path := fmt.Sprintf("/etc/docker/certs.d/%s/", cfg.registry)
// if tinkServerTLS is not enabled, skip downloading the certs
if cfg.tinkServerTLS {
Copy link

Choose a reason for hiding this comment

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

Should this not be set in parseCmdLine?

Copy link
Contributor

Choose a reason for hiding this comment

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

I say we just get rid of this. Fetching the certs is very likely to be done in an unsafe manner and we're better off not making it easy to shoot your foot.

Signed-off-by: Abhinav Pandey <abhinavmpandey08@gmail.com>
baseURL string
tinkerbell string
syslogHost string
tinkServerTLS bool
Copy link
Member

Choose a reason for hiding this comment

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

doesn't look like this value is being set anywhere. You might want to add to parseCmdLine.

@jacobweinstock jacobweinstock mentioned this pull request Nov 8, 2022
3 tasks
@jacobweinstock
Copy link
Member

This functionality now exist in main via #150

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