If there&#39;s a running pod with mounted PV from the PVC,

    kubectl -n &lt;namespace&gt; exec &lt;pod-name&gt; df

...will list all file systems, including the mounted volumes, and their free disk space.


You can monitorize them with kubelet prometheus metrics:

    kubelet_volume_stats_available_bytes{persistentvolumeclaim=&quot;your-pvc&quot;}
    kubelet_volume_stats_capacity_bytes{persistentvolumeclaim=&quot;your-pvc&quot;}

I wrote a [script][1] that lists all the PVCs in a cluster in a format similar to `df`.

You can run it via:

`./kubedf`

or:

`./kubedf -h`

for a human readable output.

Edit: The script no longer requires `kubectl proxy` to be running

  [1]: https://gist.github.com/redmcg/60cfff7bca6f32969188008ad4a44c9a

Adding to @apisim&#39;s answer if you add -h parameter then you can get details in human readable format. Something like this,

    kubectl -n &lt;namespace&gt; exec &lt;pod-name&gt; -- df -h

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/0ZkZi.png

If you are using NFS:

```
sudo apt update
sudo apt install ncdu
cd /your_nfs/kubernetes/
sudo ncdu .
```

```
ncdu 1.12 ~ Use the arrow keys to navigate, press ? for help
--- /your_nfs/kubernetes/ ----------------------------------------------------------------------------------
   34.1 GiB [##########] /backups
    2.1 GiB [          ] /redis
    1.9 GiB [          ] /XXX
  785.5 MiB [          ] /postgresql
  435.7 MiB [          ] /XXX
  391.2 MiB [          ] /XXX
```

Press `C` to see number/count of files.

I am new to react-testing-library / jest and attempting to write a test to see if the navigation of routes (using react-router-dom) is performed correctly.  So far I have been following the [README][1] and this [tutorial][2] on how to use.

One of my components uses scrollIntoView in a local function and this causes the test to fail.  

    TypeError: this.messagesEnd.scrollIntoView is not a function

      45 |
      46 |     scrollToBottom = () =&gt; {
    &gt; 47 |         this.messagesEnd.scrollIntoView({ behavior: &quot;smooth&quot; });
         |                          ^
      48 |     }
      49 |
      50 | 

This is the function in my chatbot component:

    componentDidUpdate() {
        this.scrollToBottom();
    }

    scrollToBottom = () =&gt; {
        this.messagesEnd.scrollIntoView({ behavior: &quot;smooth&quot; });
    }

And this is a sample of the tests that fail:

    test(&#39;&lt;App&gt; default screen&#39;, () =&gt; {

        const { getByTestId, getByText } = renderWithRouter(&lt;App /&gt;)
    
        expect(getByTestId(&#39;index&#39;))

        const leftClick = {button: 0}
        fireEvent.click(getByText(&#39;View Chatbot&#39;), leftClick) &lt;-- test fails

        expect(getByTestId(&#39;chatbot&#39;))
    
    })

I have tried to use a mock function, however the error still remains.

This is where this.messageEnd is assigned:

        &lt;div className=&quot;chatbot&quot;&gt;
            &lt;div className=&quot;chatbot-messages&quot;&gt;
                //render messages here
            &lt;/div&gt;
            &lt;div className=&quot;chatbot-actions&quot; ref={(el) =&gt; { this.messagesEnd = el; }}&gt;
                //inputs for message actions here
            &lt;/div&gt;
        &lt;/div&gt;

I referenced code from this stack overflow question: [How to scroll to bottom in react?][3]

**SOLUTION**

    test(&#39;&lt;App&gt; default screen&#39;, () =&gt; {

        window.HTMLElement.prototype.scrollIntoView = function() {};

        const { getByTestId, getByText } = renderWithRouter(&lt;App /&gt;)

        expect(getByTestId(&#39;index&#39;))

        const leftClick = {button: 0}
        fireEvent.click(getByText(&#39;View Chatbot&#39;), leftClick)

        expect(getByTestId(&#39;chatbot&#39;))

    })


  [1]: https://github.com/kentcdodds/react-testing-library
  [2]: https://github.com/kentcdodds/react-testing-library/blob/master/examples/__tests__/react-router.js
  [3]: https://stackoverflow.com/questions/37620694/how-to-scroll-to-bottom-in-react

TypeError: scrollIntoView is not a function

I&#39;ve followed the tutorial [here](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Scenario2.html) to create a VPC with public and private subnets.

Then I set up an AWS lambda function inside the public subnet to test if it could connect to the outside internet.

Here&#39;s my lambda function written in python3

    import requests
    
    def lambda_handler(event, context):
        r = requests.get(&#39;http://www.google.com&#39;)
        print(r)

The function above failed to fetch the content of `http://www.google.com` when I set it inside the public subnet in a VPC.

Here&#39;s the error message:

&gt; &quot;errorMessage&quot;: &quot;HTTPConnectionPool(host=&#39;www.google.com&#39;, port=80):
&gt; Max retries exceeded with url: / (Caused by
&gt; NewConnectionError(&#39;&lt;urllib3.connection.HTTPConnection object at
&gt; 0x7fd068bb8400&gt;: Failed to establish a new connection: [Errno 110]
&gt; Connection timed out&#39;,))&quot;,   &quot;errorType&quot;: &quot;ConnectionError&quot;,

I don&#39;t understand why.

The route table of the public subnet looks like this:

[![enter image description here][1]][1]

The `GET` request to `http://www.google.com` should match `igw-XXXXXXXXX` target. Why can&#39;t the internet-gateway(igw) deliver the request to `http://www.google.com` and get back the website content?

This [article](https://aws.amazon.com/premiumsupport/knowledge-center/internet-access-lambda-function/) says that I must set the lambda function inside the private subnet in order to have internet access.

&gt; If your Lambda function needs to access private VPC resources (for
&gt; example, an Amazon RDS DB instance or Amazon EC2 instance), you must
&gt; associate the function with a VPC. If your function also requires
&gt; internet access (for example, to reach a public AWS service endpoint),
&gt; your function must use a NAT gateway or instance.

But it doesn&#39;t explain why I can&#39;t set the lambda function inside the public subnet.

  [1]: https://i.stack.imgur.com/0AfBe.png

Why can&#39;t an AWS lambda function inside a public subnet in a VPC connect to the internet?

I have a Kubernetes cluster on Google Cloud Platform. It has a persistent Volume Claim with a Capacity of 1GB. The persistent volume claim is bound to many deployments. 

I would like to identify the space left in the persistent Volume Claim in order to know if 1GB is sufficient for my application. 

I have used the command &quot;kubectl get pv&quot; but this does not show the storage space left.





How to identify the storage space left in a persistent volume claim?

I have a Kubernetes cluster on Google Cloud Platform. It has a persistent Volume Claim with a Capacity of 1GB. The persistent volume claim is bound to many deployments.
I would like to identify the space left in the persistent Volume Claim in order to know if 1GB is sufficient for my application.
I have used the command "kubectl get pv" but this does not show the storage space left.

I want to create a secret for my kubernetes cluster. So I composed following `dummy-secret.yaml` file:

&lt;!-- language: yaml --&gt;

    apiVersion: v1
    kind: Secret
    metadata:
      name: dummy-secret
    type: Opaque
    data:
      API_KEY: bWVnYV9zZWNyZXRfa2V5
      API_SECRET: cmVhbGx5X3NlY3JldF92YWx1ZTE=

When I run `kubectl create -f dummy-secret.yaml` I receive back following message:

    Error from server (BadRequest): error when creating &quot;dummy-secret.yaml&quot;: Secret in version &quot;v1&quot; cannot be handled as a Secret: v1.Secret: Data: decode base64: illegal base64 data at input byte 8, error found in #10 byte of ...|Q89_Hj1Aq&quot;,&quot;API_SECR|..., bigger context ...|sion&quot;:&quot;v1&quot;,&quot;data&quot;:{&quot;API_KEY&quot;:&quot;af76fsdK_cQ89_Hj1Aq&quot;,&quot;API_SECRET&quot;:&quot;bsdfmkwegwegwe&quot;},&quot;kind&quot;:&quot;Secret&quot;,&quot;m|...

Not sure why it happens. 

As I understood, I need to encode all values under the `data` key in the yaml file. So I did base64 encoding, but kubernetes still doesn&#39;t handle the yaml secret file as I expect.

**UPDATE:**

I used this command to encode `data` values on my mac:

    echo -n &#39;mega_secret_key&#39; | openssl base64

Can&#39;t create Secret in Kubernetes: illegal base64 data at input

In Kelsey Hightower&#39;s Kubernetes Up and Running, he gives two commands :

`kubectl get daemonSets --namespace=kube-system kube-proxy`

and

`kubectl get deployments --namespace=kube-system kube-dns`

Why does one use daemonSets and the other deployments?
And what&#39;s the difference?


Difference between daemonsets and deployments

I am doing a lab about kubernetes in google cloud.  
I have create the YAML file, but when I am trying to deploy it a shell shows me this error:  

    error converting YAML to JSON: yaml: line 34: did not find expected key

YAML file:

    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: nginx
      labels:
        app: nginx
    spec:
      replicas: 2
      selector:
        matchLabels:
          app: nginx
        spec:
          volumes:
          - name: nginx-config
            configMap:
              name: nginx-config
          - name: php-config
            configMap:
              name: php-config
          containers:
          - image: php-fpm:7.2
            name: php
            ports:
            - containerPort: 9000
            volumeMounts:
            - name: persistent-storage
              mountPath: /var/www/data
            - name: php-config
              mountPath: /usr/local/etc/php-fpm.d/www.conf
              subPath: www.conf
          - image: nginx:latest
            name: nginx
            - containerPort: 80
            volumeMounts:
            - name: persistent-storage
              mountPath: /var/www/data
            - name: nginx-config
              mountPath: /etc/nginx/nginx.conf
              subPath: nginx.conf
          volumes:
            - name: persistent-storage
              persistentVolumeClaim:
                claimName: nfs-pvc

error converting YAML to JSON, did not find expected key kubernetes

I am trying to see how much memory and CPU is utilized by a kubernetes pod. I ran the following command for this:

    kubectl top pod podname --namespace=default

I am getting the following error:

    W0205 15:14:47.248366    2767 top_pod.go:190] Metrics not available for pod default/podname, age: 190h57m1.248339485s
    error: Metrics not available for pod default/podname, age: 190h57m1.248339485s

1. What do I do about this error? Is there any other way to get CPU and memory usage of the pod?
2. I saw the sample output of this command which shows CPU as 250m. How is this to be interpreted?

3. Do we get the same output if we enter the pod and run the linux `top` command?


Checking kubernetes pod CPU and memory

I have a MySQL pod running in my cluster.&lt;br&gt; I need to temporarily pause the pod from working without deleting it, something similar to docker where the `docker stop container-id` cmd will stop the container not delete the container.&lt;br&gt; Are there any commands available in kubernetes to pause/stop a pod?

how to stop/pause a pod in kubernetes

I&#39;ve increased for my quota of NVIDIA K80, and received the request approval. Why am I still not able to use a VM with GPUs?

Error as shown in title.

GCP error: Quota &#39;GPUS_ALL_REGIONS&#39; exceeded. Limit: 0.0 globally

I have a stripe webhook that call a Firebase function. In this function I need to verify that this request comes from Stripe servers. Here is the code :

```typescript
const functions = require(&#39;firebase-functions&#39;);
const bodyParser = require(&#39;body-parser&#39;);
const stripe = require(&quot;stripe&quot;)(&quot;sk_test_****&quot;);
const endpointSecret = &#39;whsec_****&#39;;
const app = require(&#39;express&#39;)();

app.use(bodyParser.json({
    verify: function (req, res, buf) {
        var url = req.originalUrl;
        if (url.startsWith(&#39;/webhook&#39;)) {
            req.rawBody = buf.toString()
        }
    }
}));

app.post(&#39;/webhook/example&#39;, (req, res) =&gt; {
    let sig = req.headers[&quot;stripe-signature&quot;];

    try {
        console.log(req.bodyRaw)
        let event = stripe.webhooks.constructEvent(req.body, sig, endpointSecret);
        console.log(event);
        res.status(200).end()

        // Do something with event
    }
    catch (err) {
        console.log(err);
        res.status(400).end()
    }
});

exports.app = functions.https.onRequest(app);
```

As mentioned in [Stripe Documentation][1], I have to use raw body to perform this security check.

I have tried with my current code and with :

```typescript
app.use(require(&#39;body-parser&#39;).raw({type: &#39;*/*&#39;}));
```

But I always get this error :

    Error: No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe? https://github.com/stripe/stripe-node#webhook-signing

  [1]: https://stripe.com/docs/webhooks/signatures

Stripe Error: No signatures found matching the expected signature for payload

In some of my Apache Airflow installations, DAGs or tasks that are scheduled to run do not run even when the scheduler doesn&#39;t appear to be fully loaded. How can I increase the number of DAGs or tasks that can run concurrently?

Similarly, if my installation is under high load and I want to limit how quickly my Airflow workers pull queued tasks (such as to reduce resource consumption), what can I adjust to reduce the average load?

How to control the parallelism or concurrency of an Airflow installation?

I added an application logo by mistake on the OAuth consent screen (URL: https://console.cloud.google.com/apis/credentials/consent), and now it says my consent screen requires verification by Google. 

Is there any way to remove the application logo from the consent screen?

**Edit:**
I didn&#39;t make it clear before but I wanted to remove the logo to get rid of the verification notice.

OAuth consent screen - ability to remove application logo

We are using GCP&#39;s Firebase with Firestore for a new mobile app we are developing. As part of this effort we need to deploy a number of cloud functions which will act as Firestore triggers for doing some back end processing. 

Our intention is to keep the deploys encapsulated inside of Firebase by using the firebase cli tools. However when we attempt to initiate the Firebase project for functions using the &quot;firebase init functions&quot; call the only two language options are &quot;Javascript&quot; and &quot;Typescript&quot;, and the only deployable stack seems to be Node.js. 

On previous GCP projects we had deployed Python based cloud functions (using the gcloud cli) and ideally we&#39;d like to continue using Python for our Firebase cloud functions.  So my questions are:
 
1. is it possible to deploy Python-based Firebase cloud functions? If not:

2. can we simply go back to deploying Python-based GCP cloud functions using the gcloud cli and still have them work as Firestore triggers?

Thanks

Content Type	Original Author	Original Content on Stackoverflow
Question	ilegolas	View Question on Stackoverflow
Solution 1 - Kubernetes	apisim	View Answer on Stackoverflow
Solution 2 - Kubernetes	Chus	View Answer on Stackoverflow
Solution 3 - Kubernetes	Brendan McGrath	View Answer on Stackoverflow
Solution 4 - Kubernetes	nandeesh	View Answer on Stackoverflow
Solution 5 - Kubernetes	qräbnö	View Answer on Stackoverflow

How to identify the storage space left in a persistent volume claim?

Kubernetes Problem Overview

Kubernetes Solutions

Solution 1 - Kubernetes

Solution 2 - Kubernetes

Solution 3 - Kubernetes

Solution 4 - Kubernetes

Solution 5 - Kubernetes

Why can't an AWS lambda function inside a public subnet in a VPC connect to the internet?

TypeError: scrollIntoView is not a function

Attributions