aws-ebs

Create snapshots of multiple EBS volumes using Terraform

◇◆丶佛笑我妖孽 提交于 2020-01-03 04:33:14
问题 I am trying to create snapshots of certain EBS volumes based on tags in a particular AWS region using Terraform. I have tried filtering EBS volumes based on Tags. I can get a clear output of EBS volume id when only one tag value is specified in the filter attribute but for more than one values, i get the following error: data.aws_ebs_volume.ebs_volume: data.aws_ebs_volume.ebs_volume: Your query returned more than one result. Please try a more specific search criteria, or set most_recent

How to mount a postgresql volume using Aws EBS in Kubernete

耗尽温柔 提交于 2020-01-01 01:15:11
问题 I've created the persistent volume (EBS 10G) and corresponding persistent volume claim first. But when I try to deploy the postgresql pods as below (yaml file) : test-postgresql.yaml Receive the errors from pod: initdb: directory "/var/lib/postgresql/data" exists but is not empty It contains a lost+found directory, perhaps due to it being a mount point. Using a mount point directly as the data directory is not recommended. Create a subdirectory under the mount point. Why the pod can't use

Kubernetes PVC with ReadWriteMany on AWS

送分小仙女□ 提交于 2019-12-21 09:39:03
问题 I want to setup a PVC on AWS, where I need ReadWriteMany as access mode. Unfortunately, EBS only supports ReadWriteOnce . How could I solve this? I have seen that there is a beta provider for AWS EFS which supports ReadWriteMany , but as said, this is still beta, and its installation looks somewhat flaky. I could use node affinity to force all pods that rely on the EBS volume to a single node, and stay with ReadWriteOnce , but this limits scalability. Are there any other ways of how to solve

Need help on volume mount issue with kubernetes

拈花ヽ惹草 提交于 2019-12-10 06:17:53
问题 I have RBAC enabled kubernetes cluster created using kops version 1.8.0-beta.1 , I am trying to run a nginx pod which should attach pre-created EBS volume and pod should start. But getting issue as not authorized even though i am a admin user. Any help would be highly appreciated. kubectl version Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.3", GitCommit:"f0efb3cb883751c5ffdbe6d515f3cb4fbe7b7acd", GitTreeState:"clean", BuildDate:"2017-11-09T07:27:47Z", GoVersion:"go1.9

Changes required to create AMI from OS disk EBS volume manually

流过昼夜 提交于 2019-12-08 19:01:37
问题 I have a VMware VM whose OS raw disk is backed up to AWS S3 . I can create AMI from the OS disk raw using import-image . I cannot use import-image everytime because it is extremely slow and because I am creating an application where you can backup your VM to AWS cloud, where in the first backup will be FULL backup which will take longer, but the consequent INCREMENTAL backup should take very less time(depending on the amount of data changed).I am creating AMI during every backup i.e. FULL or

AWS errors when installing requirements with python 2.7 when EB environment is python 3.6

[亡魂溺海] 提交于 2019-12-08 07:41:12
问题 How do I get the aWS EB instance to use the python 3 version that is already installed on the instance? I can't get a new environment running with Python 3.6 running Django 2.1+. Local (not in virtual env): which python -> /usr/local/bin/python python -V -> Python 2.7.15 which python3 -> /usr/local/bin/python3 python3 -V -> Python 3.6.5 which pip -> /usr/local/bin/pip pip -V -> pip 18.0 from /usr/local/lib/python3.6/site-packages/pip (python 3.6)` which pip3 -> /usr/local/bin/pip3 pip3 -V ->

Need help on volume mount issue with kubernetes

落花浮王杯 提交于 2019-12-05 16:49:16
I have RBAC enabled kubernetes cluster created using kops version 1.8.0-beta.1 , I am trying to run a nginx pod which should attach pre-created EBS volume and pod should start. But getting issue as not authorized even though i am a admin user. Any help would be highly appreciated. kubectl version Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.3", GitCommit:"f0efb3cb883751c5ffdbe6d515f3cb4fbe7b7acd", GitTreeState:"clean", BuildDate:"2017-11-09T07:27:47Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"8",

Kubernetes PVC with ReadWriteMany on AWS

落花浮王杯 提交于 2019-12-04 03:38:27
I want to setup a PVC on AWS, where I need ReadWriteMany as access mode. Unfortunately, EBS only supports ReadWriteOnce . How could I solve this? I have seen that there is a beta provider for AWS EFS which supports ReadWriteMany , but as said, this is still beta, and its installation looks somewhat flaky. I could use node affinity to force all pods that rely on the EBS volume to a single node, and stay with ReadWriteOnce , but this limits scalability. Are there any other ways of how to solve this? Basically, what I need is a way to store data in a persistent way to share it across pods that