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.

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

SetHostnameAsFQDN option is added to all components. Default is true #302

Merged
merged 3 commits into from
Jun 27, 2024

Conversation

qurname2
Copy link
Collaborator

No description provided.

if diff := cmp.Compare(slices.Index(statusOrder, a.Status), slices.Index(statusOrder, b.Status)); diff != 0 {
return diff
}
return a.LastTransitionTime.Compare(b.LastTransitionTime.Time)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Our linter test didn't catch that last time? =/

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Looks like not

Copy link
Collaborator

Choose a reason for hiding this comment

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

shouln't diff be gone after 6a6f343 ?
Maybe need to rebase

@kruftik
Copy link
Collaborator

kruftik commented Jun 27, 2024

it seems the added options isn't used in podtemplate generation. it still has the hardcoded true value there

Copy link
Collaborator

@l0kix2 l0kix2 left a comment

Choose a reason for hiding this comment

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

Agree with @kruftik, it looks that it must be passed deeper.
And also, maybe we can set this default in one place in the server, not every component?
Or use default in spec

@l0kix2
Copy link
Collaborator

l0kix2 commented Jun 27, 2024

I suggest we use spec default true for simplicity and check for the diff when will update ytop. If there is a diff — will mention in the release notes

@qurname2
Copy link
Collaborator Author

qurname2 commented Jun 27, 2024

Agree with @kruftik, it looks that it must be passed deeper. And also, maybe we can set this default in one place in the server, not every component? Or use default in spec

@l0kix2 yes, I think we can set true in server and check InstanceSpec if this option is exists

@l0kix2
Copy link
Collaborator

l0kix2 commented Jun 27, 2024

Agree with @kruftik, it looks that it must be passed deeper. And also, maybe we can set this default in one place in the server, not every component? Or use default in spec

@l0kix2 yes, I think we can set true in server and check InstanceSpec if this option is exists

lets just use the value from the spec and set //+kubebuilder:default:=true in the spec and see if it is visible in diff, we have defaults in spec already anyways.

Copy link
Collaborator

@l0kix2 l0kix2 left a comment

Choose a reason for hiding this comment

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

LGTM if default works and we not making field = false for users.

@l0kix2
Copy link
Collaborator

l0kix2 commented Jun 27, 2024

Fix #295

@l0kix2 l0kix2 merged commit b556530 into ytsaurus:main Jun 27, 2024
5 checks passed
leo-astorsky pushed a commit to leo-astorsky/yt-k8s-operator that referenced this pull request Aug 13, 2024
…tsaurus#302)

* SetHostnameAsFQDN option is added to all components. Default is true

* SetHostnameAsFQDN is true by default and the value is getting from instanceSpec in one place in server.go

* forgot lint-generated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants