-
Notifications
You must be signed in to change notification settings - Fork 40.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
isolate logging resources in separate namespace #68004
Conversation
/assign coffeepac |
thanks for the PR /kind feature |
/ok-to-test |
/test pull-kubernetes-e2e-kops-aws |
I think this will break updates of the addon. I am in favor of this change but we need to be careful/explicit and possibly build in some backwards compatibility somehow. a bit short on time right now, but will think more about this and maybe try some things out. @piosz do you have any thoughts on this? I think we've had this discussion before. |
kind: Namespace | ||
apiVersion: v1 | ||
metadata: | ||
name: logging |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kube-logging ?
/test pull-kubernetes-e2e-kops-aws |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
@coffeepac
What about the all the stuff in fluentd-gcp? @krmayankk |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@coffeepac updated the versions for k8s objects. |
looks good! @monotek do you have any comments or objections on this? I'm assuming the chart overrides the namespace already anyway. and we should go move the other logging thing as well. though I'm not an owner so we'll have to track someone down. |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/retest Review the full test history for this PR. Silence the bot with an |
@fejta-bot: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
@@ -28,15 +28,15 @@ rules: | |||
kind: ClusterRoleBinding | |||
apiVersion: rbac.authorization.k8s.io/v1 | |||
metadata: | |||
namespace: kube-system | |||
namespace: logging |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ClusterRoleBinding is not namespaced.
This line should be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch, thank you, please remove this line @saravanan30erd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@coffeepac Its done
template: | ||
metadata: | ||
labels: | ||
k8s-app: elasticsearch-logging | ||
version: v7.4.3 | ||
version: v7.4.4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- image: quay.io/fluentd_elasticsearch/elasticsearch:v7.4.3
The image here is 7.4.3.
Why the version is changed to v7.4.4 in labels?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the label version is for the entire statefulset. I believe updating the namespace is sufficient to rev the patch version at least. but the image isn't moving.
these will get back in-sync with the next minor release of the image.
/hold |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: coffeepac, monotek, saravanan30erd The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
/milestone v1.21 |
@coffeepac: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@saravanan30erd I know what the process is now. however, in order to get added to a milestone (it doesn't matter which one) I will also need to sort out a new home for this addon. it really shouldn't be in k/k anymore. |
@coffeepac this addon still in k/k or is it moved to somewhere? |
What this PR does / why we need it:
Now all the resources(ES, fluentd, kibana) are creating in kube-system namespace which supposed to have only k8s components, so isolated these resources in separate namespace
logging
.Release note: