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

[newrelic-logging] Helm Chart has Incomplete Env Variables #81

Closed
jsubirat opened this issue Jun 30, 2020 · 2 comments
Closed

[newrelic-logging] Helm Chart has Incomplete Env Variables #81

jsubirat opened this issue Jun 30, 2020 · 2 comments

Comments

@jsubirat
Copy link
Collaborator

Bug description

[Originally posted by @druidsbane in the newrelic-fluent-bit-output repository]

Version of Helm and Kubernetes

<Please provide this information, @druidsbane, @jasonchester>

Which chart?

newrelic-logging (current version)

What happened?

The pods were unable to get host status until I added:

- name: HOSTNAME
  valueFrom:
    fieldRef:
        apiVersion: v1
        fieldPath: metadata.name

This also happened on Azure Kubernetes Service (AKS) and was fixed by the above addition.

Can we get this added to the Helm chart and the regular deployment file?

More details on a fluent-bit issue: fluent/fluent-bit#850 (comment)

What you expected to happen?

<Please provide this information, @druidsbane, @jasonchester>

How to reproduce it?

<Please provide this information, @druidsbane, @jasonchester>

Kubernetes information as provided by @jasonchester:

{Major:"1", Minor:"16", 
GitVersion:"v1.16.7", GitCommit:"e2d9f8479783020904aba3de7499a49be6c75ebd", GitTreeState:"clean",
BuildDate:"2020-04-09T02:31:15Z", 
GoVersion:"go1.13.6", Compiler:"gc", 
Platform:"linux/amd64"}

Anything else we need to know?

<Please provide this information, @druidsbane, @jasonchester>

@gungorugur
Copy link

We have same issue. We've added HOSTNAME env but issue still goes on. We use aks 1.17.13. Any ideas ?

luckslovez added a commit that referenced this issue Aug 26, 2022
  - Since `hostNetwork` is set to `true`, the env var `HOSTNAME` needs to also
  be explicitely set
luckslovez added a commit that referenced this issue Aug 29, 2022
* Set HOSTNAME explicitely - #81

  - Since `hostNetwork` is set to `true`, the env var `HOSTNAME` needs to also
  be explicitely set
@jsubirat
Copy link
Collaborator Author

Addressed in PR #911

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants