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

Support configuration of multiple replicas for Rancher-logging chart components such as fluentd #33373

Closed
petertang2012 opened this issue Jun 25, 2021 · 4 comments
Assignees
Labels
area/logging release-note Note this issue in the milestone's release notes
Milestone

Comments

@petertang2012
Copy link

What kind of request is this (question/bug/enhancement/feature request):
enhancement

Steps to reproduce (least amount of steps as possible):
Install Rancher-logging chart and look at its values.yaml template.

Result:
Values.yaml from Rancher-logging chart does not provide option to configure multiple replicas for logging sub components such as fluentd.

Expected Result:
It would be great if we can adjust number of replicas for fluentd so that we can bring more resiliency.

Other details that may be helpful:
Neither the released stable version of Rancher logging nor the latest version on dev-v2.5 branch support this config.

Environment information

  • Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.5.8 with logging chart at 3.9.400 from dev-v2.5 branch
  • Installation option (single install/HA): HA
@paynejacob paynejacob self-assigned this Jun 25, 2021
@paynejacob paynejacob added this to the v2.6 milestone Jun 25, 2021
@paynejacob
Copy link
Contributor

This is already possible with fluentd.replicas

@maxisam
Copy link

maxisam commented Jul 30, 2021

@paynejacob It doesn't work

fluentd:
  livenessProbe:
    initialDelaySeconds: 30
    periodSeconds: 15
    tcpSocket:
      port: 24240
  resources: {}
  replicas: 2

rancher-logging:3.9.400
rancher 2.5.8
k8s: v1.19.9

image

@paynejacob
Copy link
Contributor

@maxisam my mistake this option will be added with v2.6.0 I will advocate for getting this back ported to v2.5.x

@maxisam
Copy link

maxisam commented Aug 2, 2021

@paynejacob Thank you! It has been a while someone response to my issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/logging release-note Note this issue in the milestone's release notes
Projects
None yet
Development

No branches or pull requests

3 participants