ansible-collections/kubernetes
2
0
Fork 0
Code Issues 8 Pull Requests 1 Actions Projects Releases 28 Wiki Activity

Support upgrading clusteer #14

New Issue
Closed
opened 2023-11-26 12:29:43 +00:00 by jon_nfc · 10 comments
jon_nfc commented 2023-11-26 12:29:43 +00:00 (Migrated from gitlab.com)
Copy Link

The following discussion from nofusscomputing/infrastructure/configuration-management/project-production!5 should be addressed:

  • @jon_nfc started a discussion: (+1 comment)

    Testing

    • test an upgrade of k3s to a cluster.

      running against current test iteration of cluster earth. 1.26.9 -> 1.26.10

    ToDo

    upgrade was successful however missing some steps to successfully complete

    • adjust upgrade to complete as part of running the play
    1. current installed version needs to be detected k3s --version
    2. (no change) conduct the upgrade
    3. another check of the installed version
    4. if different from first check, iterate over the master nodes restarting k3s and when node ready, move to next master

    service k3s restart service k3s-agent restart

    1. iterate over each slave, restart service, when ready moving onto next slave.# ToDo
The following discussion from nofusscomputing/infrastructure/configuration-management/project-production!5 should be addressed: - [ ] @jon_nfc started a [discussion](https://gitlab.com/nofusscomputing/infrastructure/configuration-management/project-production/-/merge_requests/5#note_1663047891): (+1 comment) > # Testing > > - [ ] test an upgrade of k3s to a cluster. > > > running against current test iteration of cluster earth. 1.26.9 -> 1.26.10 ># ToDo >upgrade was successful however missing some steps to successfully complete >* [ ] adjust upgrade to complete as part of running the play >1. current installed version needs to be detected `k3s --version` >1. (no change) conduct the upgrade >1. another check of the installed version >1. if different from first check, iterate over the master nodes restarting k3s and when node ready, move to next master > > `service k3s restart` `service k3s-agent restart` >1. iterate over each slave, restart service, when ready moving onto next slave.# ToDo
jon_nfc commented 2023-11-26 12:30:06 +00:00 (Migrated from gitlab.com)
Copy Link

added 2m of time spent

added 2m of time spent
jon_nfc commented 2023-11-26 12:30:07 +00:00 (Migrated from gitlab.com)
Copy Link

moved from nofusscomputing/infrastructure/configuration-management/project-production#3

moved from nofusscomputing/infrastructure/configuration-management/project-production#3
jon_nfc commented 2023-11-26 12:31:07 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in merge request nofusscomputing/infrastructure/configuration-management/project-production!5

mentioned in merge request nofusscomputing/infrastructure/configuration-management/project-production!5
jon_nfc commented 2024-03-29 05:07:31 +00:00 (Migrated from gitlab.com)
Copy Link

assigned to @jon_nfc

assigned to @jon_nfc
jon_nfc commented 2024-03-29 05:21:36 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in merge request !53

mentioned in merge request !53
jon_nfc commented 2024-03-29 07:49:18 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 05246b1759

mentioned in commit 05246b1759cfafdaa376cbdc01c0cc4e02cec3ae
jon_nfc commented 2024-03-29 09:02:34 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 53c4e1eaf7f0c10794d0db3d15df7d6832c82f15

mentioned in commit 53c4e1eaf7f0c10794d0db3d15df7d6832c82f15
jon_nfc commented 2024-03-29 09:32:10 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 4781cf398fac42eae8b7c3a9c89e18651a179bde

mentioned in commit 4781cf398fac42eae8b7c3a9c89e18651a179bde
jon_nfc commented 2024-03-29 10:52:58 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 6c4616873e

mentioned in commit 6c4616873ec636846a678c4858639fb34f7b5ac0
jon_nfc commented 2024-03-29 18:02:53 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit f139827554

mentioned in commit f139827554f992819bcb957e503f1eac0d3d5dd5
jon_nfc (Migrated from gitlab.com) closed this issue 2024-03-29 18:02:53 +00:00
jon_nfc (Migrated from gitlab.com) closed this issue 2024-03-29 18:02:53 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Bug
Used in discussion about a bug in comments or commits
CVE-2023-5764
Denotes items related to the CVE
CodeReview
Used in comments (issues/MR/commits) to denote code review related items
Documentation
Documentation items
Feature
Used in discussion about a Feature in comments or commits
Lint
Used in comments (issues/MR/commits) to denote lint tasks todo, done, fixed
Privacy
Used in comments (issues/MR/commits) to denote privacy related items
Security
Used in comments (issues/MR/commits) to denote Security related items
breaking-change
label used to denote that the issue/Merge Request does/will introduce a breaking change
bug::reproducable
Given to an issue when the bug has been confirmed as re-producable. Can also be used in comments and commits.
bug::unable to reproduce
Given to an issue when the bug that is not able to be reproduced. Can also be used in comments and commits.
code review::complete
code review::not started
code review::rejected
code review::underway
difficulty::Full Development
Level 3. Difficulty representing that the task to complete must be planned and created.
difficulty::Good First Issue
Level 1. Difficulty representing that the task is very simple and with limited knowledge can be completed.
difficulty::Prior Knowledge
Level 2. Difficulty representing that the task requires some prior knowledge of either the technology or the project for task completion.
documentation::complete
Issues, Merge Requests
documentation::no change required
Issues, Merge Requests and used to denote no documentation changes required
documentation::not started
Issues, Merge Requests
documentation::stalled
Issues, Merge Requests
documentation::underway
Issues, Merge Requests
impact::0
impact::1
impact::2
impact::3
impact::4
impact::5
ops::ansible-roles
OPS project tag
ops::automation
ops::gitlab-ci
OPS project tag
ops::marcas
OPS project tag
ops::python-gitlab-management
OPS project tag
ops::website
priority::0
priority::1
priority::2
priority::3
priority::4
priority::5
stage::Ready for Development
stage::develop
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::feedback required
stage::planning
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::test
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stale
Label given to issues/merge requests that are considered stale due to no collaboration and is a mark for closure.
triage
Tag given to issues/merge requests requiring triaging by the team.
triage::not_confidential
This tag is given by the triage bot so that URLs can be added to an issue/comment. A triage policy for NFC wide should remove this label.
type::CI / CD
type::automation
This type is used to denote an automation job
type::bug
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::compliance
type::discussion
Type for Issues. Can also be used in discussion in comments.
type::documentation
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::feature
type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::invalid
label given to tickets that require no action or are deem as invalid.
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::question
Type for Issues. Can also be used in discussion in comments.
type::security
Type for Issues and Merge Requests.
type::specification
Design specification
v1.0.0
Version that is affected
v1.0.1
Version that is affected
v1.1.0
Version that is affected
v1.1.1
Version that is affected
v1.1.2
Version that is affected
v1.10.0
Version that is affected
v1.10.1
Version that is affected
v1.10.2
Version that is affected
v1.10.3
Version that is affected
v1.11.0
Version that is affected
v1.12.0
Version that is affected
v1.13.0
Version that is affected
v1.13.1
Version that is affected
v1.13.2
Version that is affected
v1.2.0
Version that is affected
v1.3.0
Version that is affected
v1.4.0
Version that is affected
v1.5.0
Version that is affected
v1.6.0
Version that is affected
v1.7.0
Version that is affected
v1.7.1
Version that is affected
v1.7.2
Version that is affected
v1.8.0
Version that is affected
v1.8.1-a1
Version that is affected
v1.8.1-a2
Version that is affected
v1.9.0
Version that is affected
workflow::complete
Issues, Merge Requests
workflow::not ready
workflow::not ready::blocked
workflow::not started
Issues, Merge Requests
workflow::ready to commence
Issues, Merge Requests
workflow::stalled
Label given to issues/merge requests where no work has occured in x days iaw triage policy.
workflow::underway
Issues, Merge Requests
workflow::underway::develop
Area/CI-CD
Documentation changes
Area/Documentation
Documentation changes
Area/Security
This is security issue
Area/Testing
Issue or pull request related to testing
Bug
Failure to Confirm
Bug exists due to not confirming/testing code
Bug
Regression
THe bug is a regression of a feature
Bug
To be Confirmed
This bug is not confirmed
Bug
Unable to Reproduce
A developer can not re-create/re-produce the bug
Compat/Breaking
Breaking change that won't be backward compatible
Impact
Critical
1
The impact is critical in that it is blocking or prevents usage.
Impact
High
2
The impact requires that changes be made for continuted usage.
Impact
Low
4
The impact requires the user approach from a different angle for continued usage.
Impact
Medium
3
The impact requires a workaround for continued usage.
Impact
Very Low
5
The impact has a slight effect on usage.
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Priority
Very High
1
The priority is critical
Priority
Very Low
5
The priority is very low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Type
Bug
Something is not working
Type
Epic
Epic User Story
Type
Feature
Feature / Module
Type
Incident
Something occured related to a service
Type
RFE
Request for Enhancement
Type
Task
A work item that must be done
Urgency
Low
4
Prioritize this amoungst your list of things to do.
Urgency
Major
1
Urgency is so high it should have been dealt with last week.
Urgency
Medium
3
Start as soon as possible.
Urgency
Very High
2
Urgency is high enough to warrant near immediate commencement.
Urgency
Very Low
5
Add this to your list of things to do.
No Label
difficulty::Prior Knowledge
impact::0
priority::0
type::feature
Milestone
No items
No Milestone nfc_kubernetes Production Ready
Projects
Clear projects
No project
Assignees
Clear assignees
jason jon
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ansible-collections/kubernetes#14
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?