Skip to content

Conversation

sbernauer
Copy link
Member

@sbernauer sbernauer commented Oct 31, 2024

Description

Reasoning is on the code comments and changelog.
Relevant discussion: https://stackable-workspace.slack.com/archives/C0312UB3LLE/p1730312706917569?thread_ts=1730298381.528779&cid=C0312UB3LLE

Definition of Done Checklist

  • Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
  • Please make sure all these things are done and tick the boxes
# Author
- [ ] Changes are OpenShift compatible
- [ ] CRD changes approved
- [ ] CRD documentation for all fields, following the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs/style-guide).
- [ ] Helm chart can be installed and deployed operator works
- [ ] Integration tests passed (for non trivial changes)
- [ ] Changes need to be "offline" compatible
# Reviewer
- [ ] Code contains useful comments
- [ ] Code contains useful logging statements
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated. Follows the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs/style-guide).
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)
# Acceptance
- [ ] Feature Tracker has been updated
- [ ] Proper release label has been added
- [ ] [Roadmap](https://github.com/orgs/stackabletech/projects/25/views/1) has been updated

Copy link
Contributor

@nightkr nightkr left a comment

Choose a reason for hiding this comment

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

Hm, another alternative would be to add some "auto" mode to preferredAddressType that reverts to the old behaviour, so we avoid the breakage entirely.

Comment on lines +64 to +67
# As the nodes have stable addresses we expect them to have hostnames that are resolvable outside of Kubernetes.
# And yes, we know this causes problems when running on kind with the stable-nodes preset (default), as the kind node
# hostname is very likely not resolvable on the host machine.
preferredAddressType: Hostname
Copy link
Contributor

Choose a reason for hiding this comment

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

This should poobably match external-unstable

Comment on lines +44 to +48
# Ideally we would prefer the Hostname here, but up to (including) SDP 24.7 we defaulted to the IP.
# We actually defaulted to Hostname for some weeks, but noticed this breaks external access to kind clusters, as the
# local machines can not resolve the hostnames of the nodes (such as kind-control-plane).
# So we stick to the old default and re-visit the default later - after SDP 24.11 is released.
preferredAddressType: IP
Copy link
Contributor

Choose a reason for hiding this comment

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

This makes it sound like a temporary migration measure, but I suspect pretty heavily that we'll want to make this permanent.

@sbernauer
Copy link
Member Author

Superseded by #244

@sbernauer sbernauer closed this Oct 31, 2024
@lfrancke lfrancke deleted the fix/revert-address-default branch June 19, 2025 12:46
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.

3 participants