yolokube/ansible
yolokube/ansible
3
1
Fork 0
Code Issues 3 Pull requests 2 Projects Wiki Activity

REWORK PLAYBOOK main.yaml #52

New issue
Open
opened 2024-05-28 19:02:35 +02:00 by aaron · 1 comment
aaron commented 2024-05-28 19:02:35 +02:00
Owner
Copy link

We have a problem with the main.yaml playbook. It should theoretically contain all the configuration parts of the cluster. It should therefore be possible to use it for bootstrap AND at any other point in time. This is currently not possible, because it breaks for things like containerd and kubernetes installation/upgrade. Maybe we should call the respective subcharts, when only an upgrade is needed.

  • able to run playbook in any cluster condition

  • tags to run only parts of the playbook

We have a problem with the main.yaml playbook. It should theoretically contain all the configuration parts of the cluster. It should therefore be possible to use it for bootstrap AND at any other point in time. This is currently not possible, because it breaks for things like containerd and kubernetes installation/upgrade. Maybe we should call the respective subcharts, when only an upgrade is needed. - [ ] able to run playbook in any cluster condition - [ ] tags to run only parts of the playbook
aaron self-assigned this 2024-05-28 19:02:35 +02:00
aaron changed title from playbook main.yaml breaks at containerd upgrade, when new version is available to REWORK PLAYBOOK main.yaml 2024-05-28 20:31:46 +02:00
tom commented 2024-05-31 16:37:52 +02:00
Owner
Copy link

I think issue #50 is also related to that.

@aaron Should we stick with the plan we discussed, or do you have another idea?

  • remove main.yaml and insert into cluster-bootstrap.yaml
  • move system checks for service updates to own role -> reduces code duplication in playbooks
  • move all playbooks to own directory e.g. playbooks
I think issue #50 is also related to that. @aaron Should we stick with the plan we discussed, or do you have another idea? - remove `main.yaml` and insert into `cluster-bootstrap.yaml` - move system checks for service updates to own role -> reduces code duplication in playbooks - move all playbooks to own directory e.g. `playbooks`
tom added this to the Prod ready project 2024-05-31 17:42:32 +02:00
tom added this to the Prod Ready milestone 2024-05-31 17:42:35 +02:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
tn_upgrade_debian_to_13
ar-vault
ar-test
dev
No results found.
Labels
Clear labels   
system
CNI

  
system
Common

  
system
Core Deployments

  
system
Infrastructure

  
system
Storage

  
type
bug
Something is not working

  
type
enhancement
New feature

  
type
question
More information is needed

  
type
update
Software needs update

  
type
dependency-dashboard
Only for Renovate Dependency Dashboard

No labels
system
CNI
system
Common
system
Core Deployments
system
Infrastructure
system
Storage
type
bug
type
enhancement
type
question
type
update
type
dependency-dashboard
Milestone
Clear milestone
No items
No milestone
Prod Ready
Projects
Clear projects
No items
No project
Prod ready
Assignees
Clear assignees
No assignees
aaron
tom
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
yolokube/ansible#52
No description provided.