infrastructure/kubernetes_monitoring
2
0
Fork 0
Code Issues 6 Pull Requests Actions Projects Releases 3 Wiki Activity

chore: randomz #11

Merged
jon_nfc merged 13 commits from bits-and-bobs into development 2023-11-06 08:19:54 +00:00
Conversation 24 Commits 13 Files Changed 60 +737 -258
jon_nfc commented 2023-09-27 16:36:52 +00:00 (Migrated from gitlab.com)
Copy Link

!4

!4
jon_nfc commented 2023-09-27 16:37:08 +00:00 (Migrated from gitlab.com)
Copy Link

assigned to @jon_nfc

assigned to @jon_nfc
jon_nfc commented 2023-09-27 23:40:08 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 7afc6aa515

mentioned in commit 7afc6aa515db4a43ce8dc1a152f45f400fc68a39
jon_nfc commented 2023-09-27 23:40:08 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 2371adcbc5

mentioned in commit 2371adcbc5d64a27ff72b0ac45f589ccef4eb400
jon_nfc commented 2023-09-27 23:40:08 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit f73a9e462e

mentioned in commit f73a9e462e16dffbc0e17eaed3c0c78aff95d52b
jon_nfc commented 2023-09-27 23:40:08 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit cf38a4156a

mentioned in commit cf38a4156adcbdda150fe309f1f7dd97a5a3bf07
jon_nfc commented 2023-09-27 23:40:08 +00:00 (Migrated from gitlab.com)
Copy Link

added 4 commits

  • f73a9e46 - feat(grafana_agent): add prom rules
  • 2371adcb - feat(promtail): split node to seperate promtail service monitor
  • 7afc6aa5 - feat(prometheus): rule selector configurable from values.yaml
  • cf38a415 - refactor(grafana_datasources): default prom set to thanos

Compare with previous version

added 4 commits <ul><li>f73a9e46 - feat(grafana_agent): add prom rules</li><li>2371adcb - feat(promtail): split node to seperate promtail service monitor</li><li>7afc6aa5 - feat(prometheus): rule selector configurable from values.yaml</li><li>cf38a415 - refactor(grafana_datasources): default prom set to thanos</li></ul> [Compare with previous version](/nofusscomputing/projects/kubernetes_monitoring/-/merge_requests/4/diffs?diff_id=801236336&start_sha=5bb71971292b8f760e9b348652dc9df3c0dfa921)
jon_nfc commented 2023-09-27 23:49:15 +00:00 (Migrated from gitlab.com)
Copy Link

added 3h of time spent

added 3h of time spent
jon_nfc commented 2023-09-29 06:41:07 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 7b78989c95bf7eaf8ca1b78e1a70830f74eca324

mentioned in commit 7b78989c95bf7eaf8ca1b78e1a70830f74eca324
jon_nfc commented 2023-09-29 06:41:07 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 65b61ecf54

mentioned in commit 65b61ecf545800bcbf4efc7e3175951b9c6d2965
jon_nfc commented 2023-09-29 06:41:07 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 93e482572441989ffe6d279ce81ecd93ddd3f067

mentioned in commit 93e482572441989ffe6d279ce81ecd93ddd3f067
jon_nfc commented 2023-09-29 06:41:07 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 1f638182e08d09df6c1e366bf77860dbe3353b54

mentioned in commit 1f638182e08d09df6c1e366bf77860dbe3353b54
jon_nfc commented 2023-09-29 06:41:07 +00:00 (Migrated from gitlab.com)
Copy Link

added 4 commits

  • 65b61ecf - feat(graph): add ceph size/used to dashboard
  • 93e48257 - feat(network_policy): grafana policy added
  • 7b78989c - feat(network_policy): grafana agent policy added
  • 1f638182 - feat(network_policy): prometheus policy added

Compare with previous version

added 4 commits <ul><li>65b61ecf - feat(graph): add ceph size/used to dashboard</li><li>93e48257 - feat(network_policy): grafana policy added</li><li>7b78989c - feat(network_policy): grafana agent policy added</li><li>1f638182 - feat(network_policy): prometheus policy added</li></ul> [Compare with previous version](/nofusscomputing/projects/kubernetes_monitoring/-/merge_requests/4/diffs?diff_id=802549563&start_sha=cf38a4156adcbdda150fe309f1f7dd97a5a3bf07)
jon_nfc commented 2023-09-29 09:41:29 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 7164bb2e0b

mentioned in commit 7164bb2e0b5f2c5e7fb59bcb64321eabb651b08e
jon_nfc commented 2023-09-29 09:41:29 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 03affbee80

mentioned in commit 03affbee809d9e36f0930ae49ab07191e2b645a2
jon_nfc commented 2023-09-29 09:41:29 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 5c62055d2f

mentioned in commit 5c62055d2f2041b33a2ab5ff8023cf8bd6b08df1
jon_nfc commented 2023-09-29 09:41:29 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit ae35e704e3

mentioned in commit ae35e704e33bee4d2fea3390a7965a087e30acce
jon_nfc commented 2023-09-29 09:41:29 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 0c296c173e

mentioned in commit 0c296c173e786c77504fabba337b464bcde6c290
jon_nfc commented 2023-09-29 09:41:30 +00:00 (Migrated from gitlab.com)
Copy Link

added 5 commits

  • 03affbee - feat(labels): lables moved to values.yaml
  • 5c62055d - feat(NetworkPolicy): configure from values.yaml
  • ae35e704 - feat(prometheus): Network Policy added
  • 7164bb2e - feat(grafana): Network Policy added
  • 0c296c17 - feat(GrafanaAgent): Network Policy added

Compare with previous version

added 5 commits <ul><li>03affbee - feat(labels): lables moved to values.yaml</li><li>5c62055d - feat(NetworkPolicy): configure from values.yaml</li><li>ae35e704 - feat(prometheus): Network Policy added</li><li>7164bb2e - feat(grafana): Network Policy added</li><li>0c296c17 - feat(GrafanaAgent): Network Policy added</li></ul> [Compare with previous version](/nofusscomputing/projects/kubernetes_monitoring/-/merge_requests/4/diffs?diff_id=802736484&start_sha=1f638182e08d09df6c1e366bf77860dbe3353b54)
jon_nfc commented 2023-09-29 09:45:31 +00:00 (Migrated from gitlab.com)
Copy Link

added 7h of time spent

added 7h of time spent
jon_nfc commented 2023-10-21 07:45:32 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit b047f33e27

mentioned in commit b047f33e275d2e908f7e8a220944573f2e367bf7
jon_nfc commented 2023-10-21 07:45:33 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • b047f33e - feat(Grafana): Configure grafana from values.yaml

Compare with previous version

added 1 commit <ul><li>b047f33e - feat(Grafana): Configure grafana from values.yaml</li></ul> [Compare with previous version](/nofusscomputing/projects/kubernetes_monitoring/-/merge_requests/4/diffs?diff_id=822282348&start_sha=0c296c173e786c77504fabba337b464bcde6c290)
jon_nfc commented 2023-11-06 08:19:54 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 5bb7197129

mentioned in commit 5bb71971292b8f760e9b348652dc9df3c0dfa921
jon_nfc commented 2023-11-06 08:19:54 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit be0161876d

mentioned in commit be0161876d6b6868204af06255a01f08cc62c6ea
jon_nfc commented 2023-11-06 08:19:54 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 6f83fb5406

mentioned in commit 6f83fb5406216419305f703b8e202c9692a8051b
jon_nfc (Migrated from gitlab.com) merged commit 6f83fb5406 into development 2023-11-06 08:19:54 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
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
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
Milestone
No items
No Milestone
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: infrastructure/kubernetes_monitoring#11
No description provided.
Delete Branch "bits-and-bobs"

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?