Restrict kubernetes worker Nodes while configuring Jenkinsx on AWS #7960
Comments
|
If you use eks-jx terraform module for eks deployment, you would use these values: |
|
Hi ,
Thanks much for the reference , may i know in which file we do apply these
changes?
…On Thu, Sep 30, 2021 at 4:12 AM Roberto López ***@***.***> wrote:
If you use eks-jx terraform module for eks deployment, you would use these
values:
https://github.com/jenkins-x/terraform-aws-eks-jx#inputs -> volume_size
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7960 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJJ4ONXDH466K76M75MRPL3UERAYVANCNFSM5EVD7AXA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
I think you will need to read something: https://jenkins-x.io/v3/admin/setup/ and https://jenkins-x.io/v3/admin/platforms/ |
|
Thanks, I'll check it out. ;)
…On Fri, 8 Oct 2021, 11:46 am Roberto López, ***@***.***> wrote:
I think you will need to read something:
https://jenkins-x.io/v3/admin/setup/ and
https://jenkins-x.io/v3/admin/platforms/
In main.tf file in your terraform repository include this option
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7960 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJJ4ONWHXFOR67MLRSCJ3L3UF2EETANCNFSM5EVD7AXA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Once this PR is merged, you should be able to use volume_size and volume_type for launch templates. jenkins-x/terraform-aws-eks-jx#314. |
|
Awesome, thanks!
…On Fri, 8 Oct 2021, 4:23 pm ankitm123, ***@***.***> wrote:
Once this PR is merged, you should be able to use volume_size and
volume_type for launch templates. jenkins-x/terraform-aws-eks-jx#314
<jenkins-x/terraform-aws-eks-jx#314>.
The PR also has an example.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7960 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJJ4ONS3XY3MVBVSTP6XQPLUF3ER3ANCNFSM5EVD7AXA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Hi,
Can help on the below error. When i am trying to plan or apply terraform
the below error pops up . Attached main.tf file and the link i followed to
setup JX.
https://github.com/jx3-gitops-repositories/jx3-terraform-eks/blob/main/README.md
[image: image.png]
On Fri, Oct 8, 2021 at 11:28 PM Kranthi Thi ***@***.***> wrote:
Awesome, thanks!
On Fri, 8 Oct 2021, 4:23 pm ankitm123, ***@***.***> wrote:
> Once this PR is merged, you should be able to use volume_size and
> volume_type for launch templates. jenkins-x/terraform-aws-eks-jx#314
> <jenkins-x/terraform-aws-eks-jx#314>.
> The PR also has an example.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#7960 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AJJ4ONS3XY3MVBVSTP6XQPLUF3ER3ANCNFSM5EVD7AXA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
provider "aws" {
region = var.region
profile = var.profile
}
module "eks-jx" {
source = "jenkins-x/eks-jx/aws"
version = "1.15.12"
cluster_version = var.cluster_version
region = var.region
vault_user = var.vault_user
is_jx2 = false
jx_git_url = var.jx_git_url
jx_bot_username = var.jx_bot_username
jx_bot_token = var.jx_bot_token
force_destroy = var.force_destroy
nginx_chart_version = var.nginx_chart_version
install_kuberhealthy = var.install_kuberhealthy
}
|
|
I dont see the image, also u need to use the latest version of the module. |
|
Hi ,
Attached the error
On Tue, Oct 12, 2021 at 6:06 AM ankitm123 ***@***.***> wrote:
I dont see the image, also u need to use the latest version of the module.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7960 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJJ4ONW776FZEWGOPMVG5PDUGQXEPANCNFSM5EVD7AXA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
learn-terraform-docker-container/JXINFRA5$ terraform validate
╷
│ Error: Unsupported argument
│
│ on main.tf line 17, in module "eks-jx":
│ 17: nginx_chart_version = var.nginx_chart_version
│
│ An argument named "nginx_chart_version" is not expected here.
|
I recently updated the documentation a bit, check it: https://jenkins-x.io/v3/admin/platforms/eks/ |
|
I have followed the below doc when run terraform plan i see below error Your query returned no results. Please change your search criteria and try again. |
|
Related to this? jx3-gitops-repositories/jx3-terraform-eks#26 (comment) Or you dont have proper access ... |
|
Hi , |
|
Most probably related to this: hashicorp/terraform-provider-aws#20588 and hashicorp/terraform-provider-aws#21225 |
|
Also you could try re-running terraform apply, and see if this issue persists ... |
|
Hi,
Getting below error while importing jx project , also cannot downgrade AWS
to 3.52
Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider
hashicorp/aws: locked provider
│ registry.terraform.io/hashicorp/aws 3.59.0 does not match configured
version constraint >= 2.23.0, >= 2.53.0, >=
│ 2.70.0, >= 3.40.0, < 3.52.0, >= 3.56.0; must use terraform init -upgrade
to allow selection of new versions
╵
ERROR: failed to load plugin jx-status: can't find latest version of
plugin: {"message":"Not Found","documentation_url":"
https://docs.github.com/rest/reference/repos#get-the-latest-release"}
error: failed to load project oconfig file from
/home/ubuntu/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx:
Validation failures in YAML file
/home/ubuntu/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx/jenkins-x.yml:
pipelineConfig.pipelines.pullRequest.pipeline.stages.0.options: Additional
property volumes is not allowed
pipelineConfig.pipelines.pullRequest.pipeline.stages.0.options: Additional
property containerOptions is not allowed
pipelineConfig.pipelines.pullRequest.pipeline.environment.0.valueFrom.secretKeyRef:
Additional property name is not allowed
***@***.***
:~/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx$
***@***.***
:~/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx$
***@***.***
:~/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx$
***@***.***:~/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx$
jx boot
ERROR: failed to load plugin jx-boot: can't find latest version of plugin:
{"message":"Not Found","documentation_url":"
https://docs.github.com/rest/reference/repos#get-the-latest-release"}
…On Thu, Oct 14, 2021 at 2:19 PM ankitm123 ***@***.***> wrote:
Also you could try re-running terraform apply, and see if this issue
persists ...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7960 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJJ4ONV27BKFUQNMCSZ3EMTUG5COJANCNFSM5EVD7AXA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Hi,
I have re-rin terraform with aws provider 3.52.0 , but facing issue with
helm. Can please guide me?
When i run terraform apply i see the below error
Warning: Helm release "vault-instance" was created but has a failed status.
Use the helm command to investigate the error, correct it, then run
Terraform again.
│
│ with module.eks-jx.module.vault.helm_release.vault-instance[0],
│ on .terraform/modules/eks-jx/modules/vault/charts.tf line 11, in resource
"helm_release" "vault-instance":
│ 11: resource "helm_release" "vault-instance" {
│
╵
╷
│ Error: timed out waiting for the condition
│
│ with module.eks-jx.module.vault.helm_release.vault-instance[0],
│ on .terraform/modules/eks-jx/modules/vault/charts.tf line 11, in resource
"helm_release" "vault-instance":
│ 11: resource "helm_release" "vault-instance" {
│
╵
╷
│ Error: Error creating IAM User jenkins-x-vault: EntityAlreadyExists: User
with name jenkins-x-vault already exists.
│ status code: 409, request id: 9aa69266-e406-4430-bb0b-56b48a1efa58
│
│ with module.eks-jx.module.vault.aws_iam_user.jenkins-x-vault[0],
│ on .terraform/modules/eks-jx/modules/vault/main.tf line 11, in resource
"aws_iam_user" "jenkins-x-vault":
│ 11: resource "aws_iam_user" "jenkins-x-vault" {
this is the charts.tf file
charts.tf
resource "helm_release" "vault-operator" {
count = local.create_vault_resources ? 1 : 0
name = "vault-operator"
chart = "vault-operator"
namespace = "jx-vault"
repository = "https://kubernetes-charts.banzaicloud.com"
version = "1.10.0"
create_namespace = true
}
resource "helm_release" "vault-instance" {
count = local.create_vault_resources ? 1 : 0
name = "vault-instance"
chart = "vault-instance"
namespace = "jx-vault"
repository = "https://jenkins-x-charts.github.io/repo"
version = "1.0.22"
depends_on = [helm_release.vault-operator]
}
…On Wed, Oct 20, 2021 at 10:24 PM Kranthi Thi ***@***.***> wrote:
Hi,
Getting below error while importing jx project , also cannot downgrade AWS
to 3.52
Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider
hashicorp/aws: locked provider
│ registry.terraform.io/hashicorp/aws 3.59.0 does not match configured
version constraint >= 2.23.0, >= 2.53.0, >=
│ 2.70.0, >= 3.40.0, < 3.52.0, >= 3.56.0; must use terraform init -upgrade
to allow selection of new versions
╵
ERROR: failed to load plugin jx-status: can't find latest version of
plugin: {"message":"Not Found","documentation_url":"
https://docs.github.com/rest/reference/repos#get-the-latest-release"}
error: failed to load project oconfig file from
/home/ubuntu/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx:
Validation failures in YAML file
/home/ubuntu/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx/jenkins-x.yml:
pipelineConfig.pipelines.pullRequest.pipeline.stages.0.options: Additional
property volumes is not allowed
pipelineConfig.pipelines.pullRequest.pipeline.stages.0.options: Additional
property containerOptions is not allowed
pipelineConfig.pipelines.pullRequest.pipeline.environment.0.valueFrom.secretKeyRef:
Additional property name is not allowed
***@***.***
:~/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx$
***@***.***
:~/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx$
***@***.***
:~/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx$
***@***.***:~/learn-terraform-docker-container/.terraform/JXINFRA9/.terraform/modules/eks-jx$
jx boot
ERROR: failed to load plugin jx-boot: can't find latest version of plugin:
{"message":"Not Found","documentation_url":"
https://docs.github.com/rest/reference/repos#get-the-latest-release"}
On Thu, Oct 14, 2021 at 2:19 PM ankitm123 ***@***.***>
wrote:
> Also you could try re-running terraform apply, and see if this issue
> persists ...
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#7960 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AJJ4ONV27BKFUQNMCSZ3EMTUG5COJANCNFSM5EVD7AXA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
|
Delete the user, and re-try? |
|
Closing this ticket, as the original issue was fixed. |
|
Hi Ankit, Have deleted and recreated the user but after the time lapse we get the same error. module.eks-jx.module.cluster.module.vpc.aws_route_table_association.public[2]: Creation complete after 1s [id=rtbassoc-0b77fb1278af30128] with module.eks-jx.module.vault.helm_release.vault-instance[0], |
|
Hi, terraform plan Enter a value: root ╷ |
|
It seems |
How do we restrict the size of VM's or worker nodes of EKS . I have followed the below document for setup but not able to restrict the size of worker nodes VM's.
https://jenkins-x.io/v3/admin/platforms/eks/
The text was updated successfully, but these errors were encountered: