Skip to content

Instantly share code, notes, and snippets.

@robzienert

robzienert/keel-network-interface.yml

Last active March 29, 2018 06:33
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save robzienert/f220b7cf093dc20a2c3b052ae0bd6a9e to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save robzienert/f220b7cf093dc20a2c3b052ae0bd6a9e to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. robzienert renamed this gist Mar 29, 2018. 1 changed file with 1 addition and 4 deletions.
    5 changes: 1 addition & 4 deletions keel-network-interface.md → keel-network-interface.yml
    View file
    Original file line number Diff line number Diff line change
    @@ -1,12 +1,10 @@
    ```

    kind: NetworkInterface
    spec:
    name: "helloworld"
    securityGroups: []
    # ... Stuff
    ```

    ```
    # Displays allowed use of SpEL; in this case NetworkInterface allows an iterable spec interface.
    # `${ loop.count }` and other loop vars are made available automatically by `IterableSpec`
    # `NetworkInterfacePoolSpec : NetworkInterfaceSpec, IterableSpec<NetworkInterfaceSpec>`. The
    @@ -26,4 +24,3 @@ spec:
    # way, way, way down the line (2019?), could do something like...
    # standard notify message any time the cluster state changes (attach, detach, etc)
    onChange: "sns:arn"
    ```
  2. robzienert created this gist Mar 29, 2018.
    29 changes: 29 additions & 0 deletions keel-network-interface.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,29 @@
    ```
    kind: NetworkInterface
    spec:
    name: "helloworld"
    securityGroups: []
    # ... Stuff
    ```

    ```
    # Displays allowed use of SpEL; in this case NetworkInterface allows an iterable spec interface.
    # `${ loop.count }` and other loop vars are made available automatically by `IterableSpec`
    # `NetworkInterfacePoolSpec : NetworkInterfaceSpec, IterableSpec<NetworkInterfaceSpec>`. The
    # interface then knows what the schema is for processing `NetworkInterfacePoolSpec`.
    kind: NetworkInterfacePool
    spec:
    kind: ClusterBound
    # Simple: Just creates the pool with the defined configuration
    # ClusterBound: Will automatically attempt to bind the network interfaces to servers in the
    # defined cluster. Will bind using `apply` strategy.
    count: 20
    name: "helloworld-${ loop.count }"
    # more fields defined by NetworkInterfaceSpec
    cluster:
    name: "myapp-helloworld"
    apply: newest # any|newest
    # way, way, way down the line (2019?), could do something like...
    # standard notify message any time the cluster state changes (attach, detach, etc)
    onChange: "sns:arn"
    ```