{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":248725212,"defaultBranch":"master","name":"kube-state-metrics","ownerLogin":"dgrisonnet","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2020-03-20T10:13:33.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/22327577?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1701449420.0","currentOid":""},"activityList":{"items":[{"before":"bdb1b9e9afdfe778c4eeccde5382cb6b83687816","after":"8539a090a18c5584ee4ac4b06de9d52d323c5e54","ref":"refs/heads/bump-2.10.1","pushedAt":"2023-12-04T08:01:07.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dgrisonnet","name":"Damien Grisonnet","path":"/dgrisonnet","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22327577?s=80&v=4"},"commit":{"message":"vendor: update\n\nSigned-off-by: Damien Grisonnet ","shortMessageHtmlLink":"vendor: update"}},{"before":null,"after":"bdb1b9e9afdfe778c4eeccde5382cb6b83687816","ref":"refs/heads/bump-2.10.1","pushedAt":"2023-12-01T16:50:20.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"dgrisonnet","name":"Damien Grisonnet","path":"/dgrisonnet","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22327577?s=80&v=4"},"commit":{"message":"Merge tag 'v2.10.1' into bump-2.10.1","shortMessageHtmlLink":"Merge tag 'v2.10.1' into bump-2.10.1"}},{"before":null,"after":"cf00170dd4bebba6268dc671ad1e6b507d92ffec","ref":"refs/heads/fix-regression","pushedAt":"2023-09-12T07:46:20.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"dgrisonnet","name":"Damien Grisonnet","path":"/dgrisonnet","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22327577?s=80&v=4"},"commit":{"message":"store: fix missing cluster-scoped resources\n\nSigned-off-by: Damien Grisonnet ","shortMessageHtmlLink":"store: fix missing cluster-scoped resources"}},{"before":"7bcfa5749ffb21dcc7f467da18f8811041d159b5","after":"6f7269858dc0596d55675a4270e285a3e0fe9dd9","ref":"refs/heads/allowlist-doc","pushedAt":"2023-08-23T09:47:46.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"dgrisonnet","name":"Damien Grisonnet","path":"/dgrisonnet","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22327577?s=80&v=4"},"commit":{"message":"options: update labels/annotations allowlist doc\n\nSigned-off-by: Damien Grisonnet ","shortMessageHtmlLink":"options: update labels/annotations allowlist doc"}},{"before":null,"after":"7bcfa5749ffb21dcc7f467da18f8811041d159b5","ref":"refs/heads/allowlist-doc","pushedAt":"2023-08-22T15:55:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"dgrisonnet","name":"Damien Grisonnet","path":"/dgrisonnet","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22327577?s=80&v=4"},"commit":{"message":"options: update labels/annotations allowlist doc\n\nSigned-off-by: Damien Grisonnet ","shortMessageHtmlLink":"options: update labels/annotations allowlist doc"}},{"before":"a45a420f23ecb5c3cb46c641912761fbee0d6fab","after":"229befd41d8bc69b1ad5ecbec32e79a664531de6","ref":"refs/heads/webhook-services","pushedAt":"2023-07-04T16:24:42.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"dgrisonnet","name":"Damien Grisonnet","path":"/dgrisonnet","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22327577?s=80&v=4"},"commit":{"message":"*: add webhooks client config service metrics\n\nIn order to better identify, prioritize, and debug webhook latency\nissues it is important to have a metric that would point to the resource\nit is responsible for. However, it is not possible to have that\ndimension in the metrics exposed by Kubernetes because of the unbound\ncardinality that such a label would have.\n\nThe name of the webhook could be an alternative since it usually\ncontains some information about the resource that the webhook targets,\nhowever this is not very practical to use in multi-tenants\nenvironments.\n\nA solution for these kind of platform is to tie a specific webhook to a\nnamespace in order to be able to know which tenant manages it and take\nactions depending on that. This is achieveable by leveraging the client\nconfig information of webhooks configured via WebhookConfiguration\nresources since Services are namespaced objects.\n\nWith these new metrics, users will be able to split the alerting\nseverity of webhook latency / rejection rate per namespace on top of\nbeing able to do it based on the webhook name. This is key in\nenvironment where administrators don't have control over the webhooks\ninstalled by the various tenants.\n\nSigned-off-by: Damien Grisonnet ","shortMessageHtmlLink":"*: add webhooks client config service metrics"}},{"before":"c767f0e251d75ff09cf789d4cf22dd71ff0c3f71","after":"a45a420f23ecb5c3cb46c641912761fbee0d6fab","ref":"refs/heads/webhook-services","pushedAt":"2023-07-04T16:12:43.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"dgrisonnet","name":"Damien Grisonnet","path":"/dgrisonnet","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22327577?s=80&v=4"},"commit":{"message":"*: add webhooks client config service metrics\n\nIn order to better identify, prioritize, and debug webhook latency\nissues it is important to have a metric that would point to the resource\nit is responsible for. However, it is not possible to have that\ndimension in the metrics exposed by Kubernetes because of the unbound\ncardinality that such a label would have.\n\nThe name of the webhook could be an alternative since it usually\ncontains some information about the resource that the webhook targets,\nhowever this is not very practical to use in multi-tenants\nenvironments.\n\nA solution for these kind of platform is to tie a specific webhook to a\nnamespace in order to be able to know which tenant manages it and take\nactions depending on that. This is achieveable by leveraging the client\nconfig information of webhooks configured via WebhookConfiguration\nresources since Services are namespaced objects.\n\nWith this new metrics, users will be able to split the alerting severity\nof webhook latency / rejection rate per namespaces instead of only being\nable to have one global alert.\n\nSigned-off-by: Damien Grisonnet ","shortMessageHtmlLink":"*: add webhooks client config service metrics"}},{"before":"a0b21106110ff31e17ba7f2dd83c744167fbe07e","after":"c767f0e251d75ff09cf789d4cf22dd71ff0c3f71","ref":"refs/heads/webhook-services","pushedAt":"2023-07-04T16:10:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"dgrisonnet","name":"Damien Grisonnet","path":"/dgrisonnet","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22327577?s=80&v=4"},"commit":{"message":"*: add webhooks client config service metrics\n\nIn order to better identify and clasify webhooks it is important to have\na metric that would point to the resource it is responsible for.\nHowever, it is not possible to have that dimension in the metrics\nexposed by Kubernetes because of the unbound cardinality that such a\nlabel would have.\n\nThe name of the webhook could be an alternative since it usually\ncontains some information about the resource that the webhook targets,\nhowever this is not very practical to use in multi-tenants\nenvironments.\n\nA solution for these kind of platform is to tie a specific webhook to a\nnamespace in order to be able to know which tenant manages it and take\nactions depending on that. This is achieveable by leveraging the client\nconfig information of webhooks configured via WebhookConfiguration\nresources since Services are namespaced objects.\n\nWith this new metrics, users will be able to split the alerting severity\nof webhook latency / rejection rate per namespaces instead of only being\nable to have one global alert.\n\nSigned-off-by: Damien Grisonnet ","shortMessageHtmlLink":"*: add webhooks client config service metrics"}},{"before":null,"after":"a0b21106110ff31e17ba7f2dd83c744167fbe07e","ref":"refs/heads/webhook-services","pushedAt":"2023-07-04T16:09:02.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"dgrisonnet","name":"Damien Grisonnet","path":"/dgrisonnet","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/22327577?s=80&v=4"},"commit":{"message":"*: add webhooks client config services metrics\n\nIn order to better identify and clasify webhooks it is important to have\na metric that would point to the resource it is responsible for.\nHowever, it is not possible to have that dimension in the metrics\nexposed by Kubernetes because of the unbound cardinality that such a\nlabel would have.\n\nThe name of the webhook could be an alternative since it usually\ncontains some information about the resource that the webhook targets,\nhowever this is not very practical to use in multi-tenants\nenvironments.\n\nA solution for these kind of platform is to tie a specific webhook to a\nnamespace in order to be able to know which tenant manages it and take\nactions depending on that. This is achieveable by leveraging the client\nconfig information of webhooks configured via WebhookConfiguration\nresources since Services are namespaced objects.\n\nWith this new metrics, users will be able to split the alerting severity\nof webhook latency / rejection rate per namespaces instead of only being\nable to have one global alert.\n\nSigned-off-by: Damien Grisonnet ","shortMessageHtmlLink":"*: add webhooks client config services metrics"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADwBC92gA","startCursor":null,"endCursor":null}},"title":"Activity ยท dgrisonnet/kube-state-metrics"}