Container Engine

  1. Container Engine should not only one machine type

    A cluster should have multiple machine type for various purpose (maybe CPU-intensive, memory, IO...). I can use label to select the machine type to match my purpose of pod.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add a delay flag for upgrading container clusters to support smaller clusters.

    When upgrading a smaller container cluster (3 ~ 9) nodes there should be a --delay=timeinseconds option for the 'gcloud container clusters upgrade' command. In smaller clusters destroying and recreating nodes can kill some services in my cluster if the new nodes are not starting the pods as fast as new machines are destroyed and creating. Mostly due to docker pull's which take some time to complete, for example during the last upgrade it nearly got my database cluster down. A simple flag with a delay between node deletion and creation would solve this issue since I can specify a time…

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Scale up or down number of machines, machine type in a cluster

    The machine type and number of machines should be editable within a cluster, without deleting and recreating the cluster.

    If a service is given a static IP address, that static ip should be retainable after making changes to the hardware in that cluster.

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Suggest features should be linked from the developers console feedback menu

    This forum should be linked from the developer console's feedback menu, similar to in the compute section

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add auto-scaling container clusters

    Container clusters should support auto scaling similar to compute clusters.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Container engine not creating instance template

    On Nov 6th and 13th, the container engine created an instance template when I created a new cluster. It will not do that now. Why?

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add Webhooks to pushes to Google Container Registry

    Hi,
    I was wondering if we could get a success and maybe a failure webhook for the container registry when we push? This way to automate rolling updates on Kubernetes, we can use something like Coreos' Krud or something else that listens to webhooks to trigger rolling updates on Kubernetes. This is particularly valuable if say we rolled our own Kubernetes on GCE, which I did.

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Container Engine

Categories

Feedback and Knowledge Base