Skip to content

Conversation

@k0da
Copy link
Collaborator

@k0da k0da commented May 6, 2021

Signed-off-by: Dinar Valeev dinar.valeev@absa.africa

ns1:
enabled: true
# endpoint: https://ns1.example.com
# ignoreSSL: false
Copy link
Member

Choose a reason for hiding this comment

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

ignoreSSL can stay false uncommented

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This way it will be set into deployment, which makes args list longer and hard to read. I'd leave defaults into provider's default settings

Copy link
Member

Choose a reason for hiding this comment

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

No, in case of false the if in the template will not add the parameter at all

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@ytsarev amended

Copy link
Member

Choose a reason for hiding this comment

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

@k0da but apparently not pushed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sorry, missed that you referenced example values, while I've been amending default chart values. Fixed now


ns1:
enabled: false
# endpoint: http://ns1.example.com
Copy link
Member

Choose a reason for hiding this comment

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

please mentioned in the comment that the value is optional and it defaults to managed NS1

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@ytsarev done

@k0da k0da force-pushed the ns1 branch 2 times, most recently from 14bccab to de2e682 Compare May 6, 2021 08:03
@somaritane
Copy link
Contributor

somaritane commented May 6, 2021

@k0da , @ytsarev, do we want to also propagate MinTTLSeconds? Or are we OK with default TTL?

ns1:
enabled: true
# endpoint: https://ns1.example.com
# ignoreSSL: false
Copy link
Member

Choose a reason for hiding this comment

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

@k0da but apparently not pushed?

@k0da
Copy link
Collaborator Author

k0da commented May 6, 2021

@k0da , @ytsarev, do we want to also propagate MinTTLSeconds? Or are we OK with default TTL?

Do we have need for that atm?

@ytsarev
Copy link
Member

ytsarev commented May 6, 2021

@k0da , @ytsarev, do we want to also propagate MinTTLSeconds? Or are we OK with default TTL?

Do we have need for that atm?

depends on the default. If it is higher than our 30sec we might need to override it. Overall, the collision with DNSEndpoint CR does not look convenient. I am not sure about behavior here at all btw - will minTTL override specific CR TTL value? Does it have precedence? We need to figure out. Anyway, it does not block this specific PR


ns1:
enabled: true
# endpoint: https://ns1.example.com
Copy link
Member

Choose a reason for hiding this comment

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

why do we need it in this sample?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

same as below


ns1:
enabled: true
# endpoint: https://ns1.example.com
Copy link
Member

Choose a reason for hiding this comment

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

same as above

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

dropped

Signed-off-by: Dinar Valeev <dinar.valeev@absa.africa>
Copy link
Contributor

@somaritane somaritane left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@k0da k0da merged commit afc60ee into master May 6, 2021
@k0da k0da deleted the ns1 branch May 6, 2021 08:51
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