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

add nodeName as a new parameter to support MNO usecase #108

Merged

Conversation

nishant-parekh
Copy link
Contributor

  • Pass in the nodeName with a running GM deployment for testing
  • Use this nodeName to identify the correct linuxptp-daemon pod to use in an MNO deployment
  • NodeName is stored part of the collectionConstructor and ContainerExecContext available for any collector under use

@nishant-parekh nishant-parekh changed the title add nodeName as a new parameter in order to support MNO usecase add nodeName as a new parameter to support MNO usecase Oct 7, 2024
   * Pass in the nodeName with a running GM deployment for testing
   * Use this nodeName to identify the correct linuxptp-daemon pod to use in an MNO deployment
   * NodeName is stored part of the collectionConstructor available for any collector under use
   * fix linter issues

Signed-off-by: Nishant Parekh <nparekh@redhat.com>
Copy link
Collaborator

@nocturnalastro nocturnalastro left a comment

Choose a reason for hiding this comment

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

LGTM

@nocturnalastro nocturnalastro merged commit 3fc8e3b into redhat-partner-solutions:main Oct 7, 2024
5 checks passed
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.

2 participants