Skip to content

[OCTRL-1091] Hostname resolving in environment controller#839

Open
justonedev1 wants to merge 1 commit into
masterfrom
env_hostname_filter
Open

[OCTRL-1091] Hostname resolving in environment controller#839
justonedev1 wants to merge 1 commit into
masterfrom
env_hostname_filter

Conversation

@justonedev1

Copy link
Copy Markdown
Collaborator

When passing hostname from ECS to the k8s client there were discrepancies between FQDN and just hostname, where k8s needs exact name of the node where Task should run (in k3s this is FQDN of the machine eg. mtichak-ost.cern.ch) but ECS passes just hostname (eg. mtichak-ost). This code tries find FQDN or tries to resolve the hostname to FQDN and passes it to the tasks, so they can be matched and deployed properly.

Environment CRD controller needs a way how to resolve hostname passed
from ECS to the one existing inside k8s cluster. ECS passes non fully
qualified hostname, while kubernetes needs fully qualified hostname
@justonedev1
justonedev1 requested a review from knopers8 as a code owner July 17, 2026 12:16
@justonedev1 justonedev1 changed the title Hostname resolving in environment controller [OCTRL-1091] Hostname resolving in environment controller Jul 17, 2026
Sign up for free to 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.

1 participant