From @cakrit in #8755:

When this is finalized, please state also what we'll do for k8s and especially our helm chart.

We need a section in claim/README.md that explains how users running Netdata in k8s can claim their nodes.

@cakrit or @amoss — Can either of you provide me with more information on this, or point me to another engineer who has some experience in this. I know Ilya has

Do you want to request a feature or report a bug?

Documentation improvement

In digestAuth documentation, Kubernetes section does not contain any useful example explaining how to put credentials into a file. The given example is same as users(using base

Summary

Currently Kong supports writing configuration in a file, in YAML or JSON.
To provide a more flexible configuration, especially for those running Kong in different environments (dev, staging, production), an option to write configuration in lua can be very useful.

Additional Details

There are many use-cases that come to mind:

• Using environment variables inside the d

I always use for previous version docker-compose

Alternatively, you can use the usual commands to install or upgrade Compose:

curl -L https://github.com/docker/compose/releases/download/1.25.4/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

https://github.com/docker/compose/releases/tag/1.25.4

I not see it now...

Is your feature request related to a problem? Please describe.
The drop down list for adding/editing volumes on the add/edit container page doesn't have a logical order.

Describe the solution you'd like
A simple alphabetical order would make things easier.

**What kind of request is this (question/bug/enhan

Currently when adding an item to your cart, it only updates the cart counter graphic for that browser instance, not all connected clients. Using SignalR it should be relatively straightforward to update the cart counter on all connected clients.

Expected behavior

A cancel button, or clicking on some thing in the left side bar (the word containers)

Actual behavior

You appear stuck until you find the magic behavior link

Information about the Issue

Steps to reproduce the behavior

1. ...
2. ...

Some documentation could be improved by adding some options to runsc spec to allow users to specify the command and some other common OCI options. This could also improve the getting started experience for folks who are kicking the tires with runsc.

I'm thinking of the following options:

• Option to specify the command
• Option to specify working directory
• Option to specify network names