Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Marian Steinbach
    @marians
    Dear users, we just released CLI version 0.25.0 with some fixes and usability improvements. See https://docs.giantswarm.io/reference/cli/release-notes/ for details and update instructions.
    Jérôme Gamez
    @jeromegamez

    I was wondering - is it possible to define different domains for different environments in the swarm.json file?

    If I am in the environment <org>/dev, I would like the application to be accessible at <subdomain>.gigantic.io - but when I am in <org>/prod, I would like the app to accessible at <app-prod.com>.

    Or is this only possible via the CLI options —var or —var-file?

    Jérôme Gamez
    @jeromegamez

    Perhaps answering this myself :) - if I am not completely wrong, it would also be possible to use

    "domains": {
      "80": "$GIANTSWARM_ENVIRONMENT-app.gigantic.io“
    }

    and instead of letting the CNAME record point to loadbalancer.gigantic.io point it to prod-app.gigantic.io?

    I will try that to confirm :)
    Tobias Bradtke
    @webwurst
    Hi @jeromegamez! Looks good. Does it work for you?
    Hm, maybe not..
    What is your username on Giant Swarm? You can use our chat on https://giantswarm.io/ for informations like that.
    Jérôme Gamez
    @jeromegamez

    I haven’t tried further, because I just found out about the swarmvars.json file, which seems to be even better. I have done it like this now:

    swarmvars.json:

    {
      "user/dev": {
        "appdomain": "dev.app.tld"
      },
      "user/prod": {
        "appdomain": "app.tld"
      }
    }

    swarm.json:

    "domains": {
      "80": [
        "app-$GIANTSWARM_LOGIN_NAME-$GIANTSWARM_ENVIRONMENT.gigantic.io",
        "$appdomain"
      ]
    }
    I would have liked to use just $appdomain in the swarm.json, but the $GIANTSWARM_* context variables are not evaluated when placed in the swarmvars.json file
    Jérôme Gamez
    @jeromegamez
    @webwurst I didn’t even know a chat exists on the giantswarm website - it’s Ghostery’s fault :D
    Tobias Bradtke
    @webwurst
    Ok, glad to hear it's working for you. I will have a look on the evaluation of context variables in swarmvars.json.. :)
    Marian Steinbach
    @marians
    Dear users, when you intend to use swarm update <component> to update a component's image using the latest tag, please note this bug (and workaround) we just got aware of: giantswarm/cli#527
    Marian Steinbach
    @marians
    Dear users, we currently have an unexpected service disruption of our alpha cluster on AWS. We'll have to set up a few parts of the cluster from scratch. In case you still have running services, they will be stopped soon. We'll attempt to recreate and start your services once the infrastructure is back in a functional state. We'll notify you here once we have a new status. Sorry for the inconvenience.
    Those of you running on our own bare metal cluster (leaseweb) are not affected by this downtime.
    Marian Steinbach
    @marians
    Update: The shared alpha cluster on AWS is back to normal. If you had any services running, please check if they are up and all right and please let us know if you discover anything unexpected.
    gerrit-hntschl
    @gerrit-hntschl
    hi, could it be that my volume got lost during that recovery work?
    or was it wiped during alpha cluster cleanup work?
    Tobias Bradtke
    @webwurst
    hi @gerrit-hntschl let me check this..
    Stephan
    @ZeissS
    @gerrit-hntschl hey there :) Check my PMs please.
    gerrit-hntschl
    @gerrit-hntschl
    Hi!
    I have question regarding migrating from the AWS cluster to the leaseweb cluster. As far as I understood, I have to create an organization like this swarm org create porcamiseria, then login to the new registry docker login https://registry02.giantswarm.io and then build and push images with the following name: registry02.giantswarm.io/porcamiseria/postgres. is that correct?
    I guess it ain't :D, because I get this error:
    The push refers to a repository [registry02.giantswarm.io/porcamiseria/postgres] (len: 0)
    Repository does not exist: registry02.giantswarm.io/porcamiseria/postgres
    I can push images to that registry for my old default organization (which is also my username)
    Oliver Nicolaas Ponder
    @oponder
    Hey Gerrit, seems right, just the registry02 isn't needed anymore if I recall correctly
    gerrit-hntschl
    @gerrit-hntschl
    Hi @oponder, are you sure? yesterday @ZeissS forwarded me this info:
    In the docs, we communicate the host name https://registry.giantswarm.io. In the current migration phase, this doesn't work.
    
    Please use the name https://registry02.giantswarm.io instead. This means you'll have to name your images like this:
    
    registry02.giantswarm.io/<org-name>/<image-name>:<tag>
    Oliver Nicolaas Ponder
    @oponder
    Let me double check!
    Oliver Nicolaas Ponder
    @oponder
    Hey Gerrit, I can't verify my suggestions authentic moment, in about an hour I'll be able to try things before I suggest them sorry :)
    gerrit-hntschl
    @gerrit-hntschl
    no hurries, thanks!
    Oliver Nicolaas Ponder
    @oponder
    *authentic -> at the
    Tobias Bradtke
    @webwurst
    @gerrit-hntschl I am also not able to verify this for sure atm. But for switching to Leasweb we have to adjust the configuration of your user profile. I can check on this tomorrow morning and then to the move together if that's fine for you.
    gerrit-hntschl
    @gerrit-hntschl
    yeah, that's fine
    thanks for the help!
    Oliver Nicolaas Ponder
    @oponder

    @gerrit-hntschl: just confirming that my previous advice was wrong.

    Also, I just tried the steps you followed (creating a new org) and was able to push. mind sharing the actual commands and output? (can be via PM). Could maybe be a small typo somewhere.

    gerrit-hntschl
    @gerrit-hntschl
    yeah, now it works. must have been a typo
    Tobias Bradtke
    @webwurst
    :+1: :smile:
    Marian Steinbach
    @marians
    Dear users, have you ever wondered how Giant Swarm works exactly, behind the scenes? There is fresh documentation on that: Click the Fundamentals link in our docs main navigation. There you'll find a new Architecture Overview and an article User Services Behind The Scenes.
    Rob Haswell
    @robhaswell
    hi swarmers, quick question - my instance has failed, I'm guessing because I am using registry02.giantswarm.io looking at the pull errors in the logs. can you say which is the correct registry to use now please?
    Tobias Bradtke
    @webwurst
    Hey @robhaswell, I will have a look right now
    Rob Haswell
    @robhaswell
    thanks @webwurst. if it helps my instanceid is u3x9n9tpa0at and I already have the support user added.
    Tobias Bradtke
    @webwurst
    @robhaswell: It is running again. Yes, cool that you added the support user :)
    Problem was: The service entered failed state because of some temporary error. Now you need to first still call swarm stop on that before a swarm start words again. We have an open issue, will check priority on that. This is really confusing.
    Rob Haswell
    @robhaswell
    thanks @webwurst. would be useful if you could let me know if the failure was something I could prevent or if it was a bug in GS (or something else) - can you contact me via account email or something please? probably won't idle here :D
    Tobias Bradtke
    @webwurst
    yes, will do!
    Rob Haswell
    @robhaswell
    thanks @webwurst. end transmission
    Georgi Georgieff
    @ggeorgieff
    Nice :)
    Marian Steinbach
    @marians
    Dear users, we'd like to inform you that as of our next CLI version (0.26.0), to be released soon, we send additional usage information alongside every API call. Specifically, we add an activity name like for example update-component and the full command line content used to call the CLI. This should help us understand better how you are using the CLI. There is an opt-out mechanism to disable sending the command line content, described here: https://docs.giantswarm.io/reference/cli/global-options/#disabling-command-line-tracking
    As always, we are happy to take your feedback here.
    Marian Steinbach
    @marians
    Dear users, I hope you had some great holidays and a good start into the new year!
    Marian Steinbach
    @marians
    Most of you should have gotten the information that we are closing down our free alpha cluster access with our email on December 23. Our AWS cluster has already been closed down. We have contacted the owners of running services directly to make sure you have time to migrate.
    Marian Steinbach
    @marians

    Dear users of this channel, we have decided to replace this Gitter channel with IRC channel #giantswarm on freenode. As we are now open-sourcing more and more of our software and expect to use the chat for open source product support more, IRC is just the natural choice.

    Sorry to all who liked Gitter's usability and functions. We are positive that IRC can provide for a great experience, too. See you soon at #giantswarm!