Jenkins ansible playbook
Bootstrap mac laptop
Ansible bootstrap for my home server
Sets up my RPI at home
Test auth0 app
Rules and hosted pages (lock) used for the Auth0 instances of Mozilla.
Creates an IAM user with permissions to Alexa Top site
limed/aws-node-termination-handler 0
A Kubernetes Daemonset to gracefully handle EC2 instance shutdown
Repository for AWS CLI aliases.
Bash functions for managing AWS resources simply and easily
push eventmdn/insights
commit sha 72a168649a8f893ff1c455b90a928fe27504b17e
Update packages (#44)
push time in 2 days
PR opened mozilla-it/itse-apps-prod-1-infra
Configure external-dns to only check service as a source. We're removing ingress as a source because it checks
the lists of host in the ingress object and create dns records based on that. This is less than ideal for our
situation
pr created time in 2 days
create barnchmozilla-it/itse-apps-prod-1-infra
branch : limed/external-dns-service
created branch time in 2 days
PR opened mozilla-it/itse-apps-stage-1-infra
Configure external-dns to only check service as a source. We're removing ingress as a source because it checks
the lists of host in the ingress object and create dns records based on that. This is less than ideal for our
situation
pr created time in 2 days
create barnchmozilla-it/itse-apps-stage-1-infra
branch : limed/external-dns-service
created branch time in 2 days
issue commentmdn/insights
Add link to MDN browser compatibility report to Insights site.
If there's anything special one would have to do, it would be great if the PDF URL is one where the PDF could be updated in place. I expect we'll find a few things we want to update after publication...
I completely agree that having it separate from the repo is not ideal. I am not sure what the reason was to put it on S3. Perhaps @limed knows?
If there is no specific reason, perhaps I can add the PDF to the assets folder and link to it relatively from the landing page.
Looks like the URL will be https://mdn-web-dna.s3-us-west-2.amazonaws.com/MDN-Browser-Compatibility-Report-2020.pdf, although it's still 404.
Yup, that is expected. It has not been uploaded to S3 yet.
I went and uploaded it to s3 so it should be there now
comment created time in 2 days
pull request commentmdn/insights
@schalkneethling I have no idea, I'm afraid.
I have made updates to the layout per your suggestions. I also linked the PDF and included it in the
assetsfolder but, when running it via the webpack dev server I get a 404 locally. Perhaps the dev server cannot serve PDF files or requires some config change? @limed @escattoneOr maybe it will just work when deployed to S3?
Hi @schalkneethling I can upload the file to S3 but the references to the file might need to point to S3 based on the PR
I grabbed the PDF from this PR and have uploaded it
comment created time in 2 days
PR opened mozilla-it/terraform-modules
Nothing crazy here but just a simple dns zone module
pr created time in 2 days
push eventmozilla-it/terraform-modules
commit sha c148930690e967d6cdf6ffe2aff1a52f0ecdc827
Initial commit of route53 zone module
push time in 2 days
push eventmozilla-it/terraform-modules
commit sha 9c76428a80f8fb9d13f3326cb1aff2b001eb0212
Add service account name for flux module
push time in 2 days
PR merged mozilla-it/terraform-modules
The GKE module references the service account for flux so it fails if we do not add serviceAccount.name in the locals portion
pr closed time in 2 days
PR opened mozilla-it/terraform-modules
The GKE module references the service account for flux so it fails if we do not add serviceAccount.name in the locals portion
pr created time in 2 days
push eventmozilla-it/refractr
commit sha 97c343dd37f958582c25f3e06dfbd7ff392ef9df
Fixing configs Setting appropriate domains for prod and stage
push time in 3 days
push eventmozilla-it/refractr
commit sha d1080bf9bc27a4f254509e4d2dc990d62889e097
Fixing configs Setting appropriate domains for prod and stage
push time in 3 days
push eventmozilla-it/itse-apps-stage-1-infra
commit sha 83ef8a923c2dbb8ba72a6577d4c0f46df195966f
Setting txtOwnerId for external-dns
push time in 3 days
delete branch mozilla-it/itse-apps-stage-1-infra
delete branch : limed/external-dns-tweak
delete time in 3 days
PR merged mozilla-it/itse-apps-stage-1-infra
also sneaked in an annotation change for the nlb, just adding an additional tag
pr closed time in 3 days
Pull request review commentmozilla-it/refractr
# output from refractr.py default-domains: - prod.mozilla-redirects.xyz- - stage.mozilla-redirects.xyz - refractr.mozilla.org- - refractr.allizom.org refracts: # FIXME: this is a stage only tests-- mozilla.com/: refractr1.allizom.org+- mozilla.com/: refractr1.mozilla.org # FIXME: this is a stage only tests
Fixed in c98caf9ece1e102a0515d0ec2b499209d45472d9
comment created time in 3 days
push eventmozilla-it/refractr
commit sha c98caf9ece1e102a0515d0ec2b499209d45472d9
Update comment
push time in 3 days
push eventmozilla-it/itse-apps-prod-1-infra
commit sha f99aa1589e490452d81a842bc2fe5511f9bcc791
add external DNS
commit sha 75b332d79d43aca751bc2bd3bd3c7161a889e7ff
Fixed a typo
push time in 3 days
delete branch mozilla-it/itse-apps-prod-1-infra
delete branch : limed/external-dns
delete time in 3 days
PR merged mozilla-it/itse-apps-prod-1-infra
Adds external-dns helm chart for ease of mapping dns to services
Also added some annotation to ingress-nginx controller
pr closed time in 3 days
push eventmozilla-it/itse-apps-prod-1-infra
commit sha 6ff24ab2fda2d4b4d5af6d9484593cbf8ccaa64b
Fixed a typo
push time in 3 days
PR opened mozilla-it/itse-apps-prod-1-infra
Adds external-dns helm chart for ease of mapping dns to services
Also added some annotation to ingress-nginx controller
pr created time in 3 days
create barnchmozilla-it/itse-apps-prod-1-infra
created branch time in 3 days
PR opened mozilla-it/itse-apps-stage-1-infra
also sneaked in an annotation change for the nlb, just adding an additional tag
pr created time in 3 days
create barnchmozilla-it/itse-apps-stage-1-infra
branch : limed/external-dns-tweak
created branch time in 3 days
push eventmozilla-it/itse-apps-stage-1-infra
commit sha d5e0439fdd7b1b2b5b8a055c8fb1e9684e5c0ce9
Fixing annotations
push time in 3 days
delete branch mozilla-it/itse-apps-stage-1-infra
delete branch : limed/fixing-annotations
delete time in 3 days
PR merged mozilla-it/itse-apps-stage-1-infra
Forgot to add quotes
pr closed time in 3 days
PR opened mozilla-it/itse-apps-stage-1-infra
Forgot to add quotes
pr created time in 3 days
create barnchmozilla-it/itse-apps-stage-1-infra
branch : limed/fixing-annotations
created branch time in 3 days
delete branch mozilla-it/itse-apps-stage-1-infra
delete branch : limed/external-dns
delete time in 3 days
push eventmozilla-it/itse-apps-stage-1-infra
commit sha 2342b54d425571fffd2b9efbf2b77ec71fafcf23
Add external DNS helm chart
push time in 3 days
PR merged mozilla-it/itse-apps-stage-1-infra
Added external DNS helm chart and annotated the service to include the correct hostname
Also sneaked in some upstream terraform changes
pr closed time in 3 days
PR opened mozilla-it/itse-apps-stage-1-infra
Added external DNS helm chart and annotated the service to include the correct hostname
Also sneaked in some upstream terraform changes
pr created time in 3 days
create barnchmozilla-it/itse-apps-stage-1-infra
created branch time in 3 days
push eventlimed/infra
commit sha bffc28480e0b918446ac2cc3b7f9bbba6cb5742e
Remove mdn-apps-a cluster
commit sha 32e682af73874728fd2d6f5d863dd17f7b568ffa
Merge pull request #464 from limed/limed/delete-mdn-apps-a Remove mdn-apps-a cluster
push time in 3 days
Pull request review commentmozilla-it/refractr
Separated the refractr.yml for prod and stage
if os.path.islink(__file__): DIR = os.path.abspath(REAL_PATH + "/..") CWD = os.path.abspath(os.getcwd()) REL = os.path.relpath(DIR, CWD)-SRC = f"{DIR}/refractr"-REFRACTR = f'{REL}/refractr'-REFRACTR_YML = os.getenv('REFRACTR_YML', f'{REFRACTR}/refractr.yml')-INGRESS_YAML_TEMPLATE = f'{REFRACTR}/ingress.yaml.template'-STAGE_URL='refractr.allizom.org'++STAGE_URL = 'refractr.allizom.org'
What is this URL being used for?
comment created time in 3 days
push eventmdn/infra
commit sha bffc28480e0b918446ac2cc3b7f9bbba6cb5742e
Remove mdn-apps-a cluster
commit sha 32e682af73874728fd2d6f5d863dd17f7b568ffa
Merge pull request #464 from limed/limed/delete-mdn-apps-a Remove mdn-apps-a cluster
push time in 3 days
PR merged mdn/infra
This deletes the mdn-apps-a cluster which used to host the developer-portal app as well as the module we used to create it
pr closed time in 3 days
push eventmozilla-it/itse-apps-prod-1-infra
commit sha cbd7e5a912a46850b03b0e409b589f06ad9aacc6
Create null_resource to automate CRD install
commit sha 9d9bc837c99d7f02cf93fd295147927b57adf9b0
remove validate
push time in 3 days
delete branch mozilla-it/itse-apps-prod-1-infra
delete branch : limed/crd-install
delete time in 3 days
PR merged mozilla-it/itse-apps-prod-1-infra
pr closed time in 3 days
delete branch mozilla-it/itse-apps-prod-1-infra
delete branch : create-cluster
delete time in 3 days
push eventmozilla-it/itse-apps-prod-1-infra
commit sha 83f774145d6dde144a23e2bc68e6ca218a5349ce
remove validate
push time in 3 days
Pull request review commentmozilla-it/itse-apps-prod-1-infra
Create null_resource to automate CRD install
resource "kubernetes_namespace" "cert_manager" { } } +# CRDs have to be installed differently, there is a drama about it in the community.+# TL;DR: Helm is not yet ready to upgrade CRDs and this can cause an outage.+# For more info read https://github.com/helm/helm/issues/7735+resource "null_resource" "cert_manager_crd" {+ provisioner "local-exec" {+ working_dir = path.module+ command = <<EOF+for i in `seq 1 10`; do \
It will try 10 times and sleep for 10 seconds if the k8s API is not up and running
So really this is just a retry mechanism until the k8s API is up and running
comment created time in 3 days
Pull request review commentmozilla-it/itse-apps-prod-1-infra
Create null_resource to automate CRD install
resource "kubernetes_namespace" "cert_manager" { } } +# CRDs have to be installed differently, there is a drama about it in the community.+# TL;DR: Helm is not yet ready to upgrade CRDs and this can cause an outage.+# For more info read https://github.com/helm/helm/issues/7735+resource "null_resource" "cert_manager_crd" {+ provisioner "local-exec" {+ working_dir = path.module+ command = <<EOF+for i in `seq 1 10`; do \+ echo $kube_config | base64 --decode > kube_config.yaml & \+ kubectl apply --validate=false -f ${local.cert_manager_crd_manifest} --kubeconfig kube_config.yaml && break ||
This was taken from the documentation https://hub.helm.sh/charts/jetstack/cert-manager
I'm ok to remove it
comment created time in 3 days
push eventmozilla-it/itse-apps-stage-1-infra
commit sha 171948eaa61c15b2053aae63b2d476bfe1e135a4
Adding additional outputs
push time in 4 days
delete branch mozilla-it/itse-apps-stage-1-infra
delete branch : limed/adding-outputs
delete time in 4 days
PR merged mozilla-it/itse-apps-stage-1-infra
Adding additional eip outputs and fixed some tags
pr closed time in 4 days
push eventmozilla-it/itse-apps-prod-1-infra
commit sha 0dcbc776f65c6019920c2e5d770c8a81e09884de
Add EIP for ingress-nginx
push time in 4 days
PR merged mozilla-it/itse-apps-prod-1-infra
Add a static EIP to the ingress-nginx nlb, this removes the need for global accelerator
pr closed time in 4 days
PR opened mozilla-it/itse-apps-stage-1-infra
Adding additional eip outputs and fixed some tags
pr created time in 4 days
create barnchmozilla-it/itse-apps-stage-1-infra
created branch time in 4 days
PR opened mozilla-it/itse-apps-prod-1-infra
Add a static EIP to the ingress-nginx nlb, this removes the need for global accelerator
pr created time in 4 days
PR opened mdn/infra
This deletes the mdn-apps-a cluster which used to host the developer-portal app as well as the module we used to create it
pr created time in 4 days
push eventmozilla-it/itse-apps-stage-1-infra
commit sha bcdfd6be3e72ee9d3e44b3de42770003ad7884b8
Add 2 additional EIP
push time in 5 days
delete branch mozilla-it/itse-apps-stage-1-infra
delete branch : limed/extra-eip
delete time in 5 days
PR merged mozilla-it/itse-apps-stage-1-infra
pr closed time in 5 days
PR opened mozilla-it/itse-apps-stage-1-infra
pr created time in 5 days
create barnchmozilla-it/itse-apps-stage-1-infra
created branch time in 5 days
push eventmozilla-it/itse-apps-stage-1-infra
commit sha dadf6cac974ce0c4ce4c0615c10b46d01aa5c7ff
A little experiment to see if eip's can be attached to NLB
push time in 5 days
delete branch mozilla-it/itse-apps-stage-1-infra
delete branch : limed/eip-experiment
delete time in 5 days
PR merged mozilla-it/itse-apps-stage-1-infra
pr closed time in 5 days
PR opened mozilla-it/itse-apps-stage-1-infra
pr created time in 5 days
create barnchmozilla-it/itse-apps-stage-1-infra
created branch time in 5 days
push eventmozilla-it/itse-apps-stage-1-infra
commit sha 3c6a02b2470b2dfa95c289ee089270138c3397b6
Auto install CRD
commit sha d04ff4796a18c2fa98deeedaa1a2eef50e00596d
Bump cert manager version
push time in 5 days
delete branch mozilla-it/itse-apps-stage-1-infra
delete branch : limed/crd-auto-install
delete time in 5 days