Skip to content
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

Merged
merged 3 commits into from
Apr 8, 2021

Conversation

saravanan30erd
Copy link
Contributor

@saravanan30erd saravanan30erd commented Aug 29, 2018

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:

fluentd: isolate logging resources in separate namespace

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels Aug 29, 2018
@saravanan30erd
Copy link
Contributor Author

/assign coffeepac

@neolit123
Copy link
Member

thanks for the PR
please change the release note to:
fluend: isolate logging resources in separate namespace

/kind feature
/remove-sig cluster-lifecycle
/sig instrumentation
(TODO: need to add labels for this one.)

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. and removed sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels Aug 29, 2018
@neolit123
Copy link
Member

/ok-to-test

@k8s-ci-robot k8s-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Aug 29, 2018
@saravanan30erd
Copy link
Contributor Author

/test pull-kubernetes-e2e-kops-aws
/test pull-kubernetes-e2e-gke
/test pull-kubernetes-e2e-gce

@coffeepac
Copy link
Contributor

coffeepac commented Aug 29, 2018

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kube-logging ?

@saravanan30erd
Copy link
Contributor Author

/test pull-kubernetes-e2e-kops-aws

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 21, 2018
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 19, 2019
@coffeepac
Copy link
Contributor

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 22, 2019
@monotek
Copy link
Member

monotek commented Jan 22, 2019

@coffeepac
Imho also Elasticsearch should go to the new namespace:

What about the all the stuff in fluentd-gcp?
https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/fluentd-gcp

@krmayankk
I would also keep the name "logging" as also non kube apps would use the apps in this namespace.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 28, 2019
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 16, 2021
@saravanan30erd
Copy link
Contributor Author

@coffeepac updated the versions for k8s objects.

@coffeepac
Copy link
Contributor

coffeepac commented Mar 16, 2021

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.

@coffeepac
Copy link
Contributor

/retest

Copy link
Member

@monotek monotek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 17, 2021
@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

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.

@monotek
Copy link
Member

monotek commented Mar 17, 2021

/retest

@@ -28,15 +28,15 @@ rules:
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
namespace: kube-system
namespace: logging
Copy link
Member

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.

Copy link
Contributor

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

Copy link
Contributor Author

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
Copy link
Member

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?

Copy link
Contributor

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.

@coffeepac
Copy link
Contributor

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 19, 2021
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 19, 2021
@monotek
Copy link
Member

monotek commented Mar 19, 2021

/lgtm

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 19, 2021
@coffeepac
Copy link
Contributor

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 22, 2021
@coffeepac
Copy link
Contributor

/milestone v1.21

@k8s-ci-robot
Copy link
Contributor

@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:

/milestone v1.21

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.

@coffeepac
Copy link
Contributor

@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.

@k8s-ci-robot k8s-ci-robot merged commit d8f3794 into kubernetes:master Apr 8, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.22 milestone Apr 8, 2021
@saravanan30erd
Copy link
Contributor Author

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/provider/gcp Issues or PRs related to gcp provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants