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

Apparmor #49

New issue
Closed
opened 2024-02-16 18:49:34 +01:00 by aaron · 6 comments
aaron commented 2024-02-16 18:49:34 +01:00
Owner
Copy link
No description provided.
tom added this to the Prod ready project 2024-02-17 14:52:23 +01:00
tom added this to the Prod Ready milestone 2024-02-17 14:52:27 +01:00
tom commented 2024-05-28 18:13:41 +02:00
Owner
Copy link

Update:

  • Master1 has AppArmor enabled for testing

Ready Status:

  • Master1
  • Master2
  • Master3
  • Worker1
  • Worker2
  • Worker3
Update: - Master1 has AppArmor enabled for testing Ready Status: - [x] Master1 - [ ] Master2 - [ ] Master3 - [ ] Worker1 - [ ] Worker2 - [x] Worker3
aaron commented 2024-05-28 21:06:31 +02:00
Author
Owner
Copy link

I can find no issue with master1, where it is enabled. Survived both containerd update and k8s/system update
@tom

I can find no issue with master1, where it is enabled. Survived both containerd update and k8s/system update @tom
🎉 1
aaron commented 2024-05-28 21:28:53 +02:00
Author
Owner
Copy link

Also no issue with a worker node. Survives reboot without problems.

Also no issue with a worker node. Survives reboot without problems.
👍 1
aaron commented 2024-12-05 21:31:24 +01:00
Author
Owner
Copy link

@tom any news

@tom any news
tom commented 2024-12-29 14:32:43 +01:00
Owner
Copy link

@tom any news

I once read that there were temporary problems with the standard AppArmor Kubelet profiles, but unfortunately, I can't find anything more about this. Since neither Master1 nor Worker3 have shown such errors so far, this should be solved and we can reactivate AppArmor (and remove the deactivation in the playbook). 🙂

> @tom any news > I once read that there were temporary problems with the standard AppArmor Kubelet profiles, but unfortunately, I can't find anything more about this. Since neither Master1 nor Worker3 have shown such errors so far, this should be solved and we can reactivate AppArmor (and remove the deactivation in the playbook). 🙂
aaron commented 2025-01-07 21:51:06 +01:00
Author
Owner
Copy link

PR that enables AppArmor again:
#57

PR that enables AppArmor again: #57
tom closed this issue 2025-02-01 09:07:33 +01: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
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.

Depends on
#57 enable AppArmor
yolokube/ansible
Reference
yolokube/ansible#49
No description provided.