Skip to content

[OCTRL-1091] Environment controller changes for ECS - #828

Closed
justonedev1 wants to merge 1 commit into
masterfrom
env_ctrl_ecs_bridge_requirements
Closed

[OCTRL-1091] Environment controller changes for ECS#828
justonedev1 wants to merge 1 commit into
masterfrom
env_ctrl_ecs_bridge_requirements

Conversation

@justonedev1

Copy link
Copy Markdown
Collaborator

environment controller changes for ECS bridge compatiblity

  • matching node names in cluster from partial names yaml templates
  • add taskID annotation to be able to filter tasks
  • OCC_CONTROL_PORT overwrites Spec.Control.Port of task

@knopers8knopers8 changed the title [OCTRL-1091-part] Environment controller changes for ECS[OCTRL-1091] Environment controller changes for ECSJul 7, 2026

@knopers8knopers8 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

indeed understanding the intention of each change was difficult given the PR does many things, so i might have skipped something

Comment on lines +15 to +17
securityContext:
fsGroup: 1100
supplementalGroups: [10, 1105]

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

it looks like this does not correspond to any of the three changes?

- matching node names in cluster from partial names yaml templates
- add taskID annotation to be able to filter tasks
- OCC_CONTROL_PORT overwrites Spec.Control.Port of task

can you extract to a separate PR or amend the commit?

Comment on lines +27 to +28
runAsUser: 1100
runAsGroup: 1100

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

these neither

// resolveNodeName resolves a short node name (e.g. "flp001") to the full name known to
// the cluster (e.g. "flp001.cern.ch") by checking whether any dot-separated component
// of a node's name matches exactly. Returns an error if zero or more than one node matches.
func resolveNodeName(nodes []v1.Node, nodename string) (string, error) {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Please use "nodeName" or "nodename" consistently, i.e. "name" either always starting upper or lower case. IMO "nodeName" is better, since it's two words, but I leave the final decision to you.

name: readout
namespace: alice-tasks
spec:
nodeName: mtichak-ost.cern.ch

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I am a bit lost why ".cern.ch" is needed here, but should be absent in the environment templates.

task.Spec.Arguments = make(map[string]string)
}

// TODO: check for containers!

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

remove todo?

case 1:
return matches[0], nil
default:
return "", fmt.Errorf("node name %q is ambiguous, matched: %v", nodename, matches)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

i appreciate being paranoic!

@justonedev1

Copy link
Copy Markdown
CollaboratorAuthor

you are right... I will split this into multiple PR, so it is more obvious and descriptive. I will address your remarks in those PRs

…atiblity
- matching node names in cluster from partial names yaml templates
- add taskID annotation to be able to filter tasks
- OCC_CONTROL_PORT overwrites Spec.Control.Port of task
@justonedev1
justonedev1force-pushed the env_ctrl_ecs_bridge_requirements branch from 135fec5 to 3cced8cCompareJuly 16, 2026 12:14
@justonedev1

Copy link
Copy Markdown
CollaboratorAuthor

Closed because it was split into multiple PRs

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@justonedev1@knopers8