Skip to content

add coco users for tabs - #9962

Open
esposem wants to merge 6 commits into
redhat-cop:developmentfrom
esposem:coco-users
Open

esposem wants to merge 6 commits into
redhat-cop:developmentfrom
esposem:coco-users

Conversation

@esposem

@esposem esposem commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor
SUMMARY
ISSUE TYPE
  • New role Pull Request
COMPONENT NAME
ADDITIONAL INFORMATION

esposem and others added 6 commits November 2, 2026 15:52
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
…anup on remove

- peerpod_tags default was the key1=value1 placeholder; empty now, the
  chart omits the TAGS key from peer-pods-cm unless set to something real
- az login is not a state change: changed_when: false
- remove_workload now deletes the peer pod NAT gateway, its public IP and
  the subnet association (best effort, skipped when the cluster is gone);
  the network fact derivation moved to azure-network-facts.yml, shared by
  create and remove paths, with a soft-fail mode for teardown

Co-Authored-By: Claude Code <noreply@anthropic.com>
LB1150 is back to 1 master + 0 workers. When no worker-role nodes exist,
Kata is installed on the single node (the guide's Azure SNO procedure):
the node selection falls back from worker-role nodes to the only node,
and the kata-oc MachineConfigPool wait is skipped on single-node
clusters, matching the workshop guide's SNO note. The RuntimeClass waits
still run either way.

Co-Authored-By: Claude Code <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

1 participant