!sgXEFOWtqDlGqUMWAl:matrix.org

Drogue IoT

22 Members
IoT on ARM Cortex-M using Rust1 Servers

Load older messages


SenderMessageTime
12 May 2021
@freenode_jcrossley3:matrix.orgjcrossley3why not just use $(kubectl config current-context) for the drg context name, too?15:21:40
@jbtrystram:matrix.orgjbtrystram
In reply to @freenode_jcrossley3:matrix.org
why can't "ugglyGeneratedCtxName" just be "default"?
it sounds like a reasonnable choice, but i don't like that kind of values when i come back to it a month after and have no iea why it's not working and i type drg config list to get an idea of what i was doing and seeing "default" does not help me much
15:23:54
@ctron:matrix.orgctrondid I mention using hostnames?15:24:45
@jbtrystram:matrix.orgjbtrystram
In reply to @freenode_jcrossley3:matrix.org
why not just use $(kubectl config current-context) for the drg context name, too?
i think that's what ctron suggested
15:24:47
@ctron:matrix.orgctronnope15:25:09
@ctron:matrix.orgctronI don't think we should mix kubectl and drg … as you can run drg without having installed kubectl15:25:27
@freenode_jcrossley3:matrix.orgjcrossley3 personally, i'd prefer drg was a kubectl plugin (oc plugin? kn plugin?). that way, i think we could share config and contexts. seems simpler than forcing the user to keep them in sync 15:26:47
@jbtrystram:matrix.orgjbtrystram
In reply to @jbtrystram:matrix.org
i think that's what ctron suggested
sorry i mis-expressed myself. I meant "ctron suggested we use the hostname in some way, kind of like kubectl do"
15:27:05
@jbtrystram:matrix.orgjbtrystram jcrossley3: in a "as a service" offering the user would not have kubectl set up 15:28:09
@freenode_jcrossley3:matrix.orgjcrossley3 i concede i'm thinking of it from the pov of a k8s user, i.e. when i set my kubectl context, my drg context switches, too. just like for kn, func, etc. it's a convenience for me. i don't have a good sense of what's convenient for an "aas" customer. 15:29:30
@ctron:matrix.orgctron"ass customer"? … Oh I misread that :D15:30:02
@freenode_jcrossley3:matrix.orgjcrossley3:) even for an ass customer, if they most often will have a single context, then the api should reflect that, and hide it by default, imo.15:30:44
@freenode_jcrossley3:matrix.orgjcrossley3and because hostnames are often virtual and temporary, my preference would be for some known default name rather than the hostname, which may be meaningless to me after a few weeks.15:31:56
@ctron:matrix.orgctronwell I would assume if you have only one context, you wouldn't even notice it … whatever name it has … however if you have multiple contexts, then "default" would me meaningless to me15:34:52
@jcrossley3:matrix.orgJim Crossleyi don't feel strongly about the default name15:35:30
@ctron:matrix.orgctron If you take a look at kubectl's context, they use the hostname too: name: knative-eventing/wonderful-iot-playground-org:6443/admin 15:35:38
@jcrossley3:matrix.orgJim Crossleymine's "minikube" i think :) 15:36:30
@ctron:matrix.orgctron * If you take a look at kubectl's context, they use the hostname too: name: knative-eventing/wonderful-iot-playground-org:6443/admin 15:36:45
@jbtrystram:matrix.orgjbtrystram *

proposal :
I updated drg config list to display the cluster address :

NAME   ADDRESS                                                                                                                    DEFAULT APP
foo        https://console-backend-drogue-dev.apps.wonderful.iot-playground.org/         <Not Set>
bar *     https://console-backend-drogue-dev.apps.wonderful.iot-playground.org/         <Not Set>

and will use "default" as context name when drg login is called without a -c arg. Please vote

15:48:56
@jbtrystram:matrix.orgjbtrystram

proposal :
I updated drg config list to display the cluster address :

NAME   ADDRESS                                                                                     DEFAULT APP
foo        https://console-backend-drogue-dev.apps.wonderful.iot-playground.org/         <Not Set>
bar *     https://console-backend-drogue-dev.apps.wonderful.iot-playground.org/         <Not Set>

and will use "default" as context name when drg login is called without a -c arg. Please vote

15:49:03
@jbtrystram:matrix.orgjbtrystram *

proposal :
I updated drg config list to display the cluster address :

NAME   ADDRESS                                                                                              DEFAULT APP
foo        https://console-backend-drogue-dev.apps.wonderful.iot-playground.org/         <Not Set>
bar *     https://console-backend-drogue-dev.apps.wonderful.iot-playground.org/         <Not Set>

and will use "default" as context name when drg login is called without a -c arg. Please vote

15:49:24
@jbtrystram:matrix.orgjbtrystram *

proposal :
I updated drg config list to display the cluster address :

NAME   ADDRESS                                                        DEFAULT APP
foo        https://console-backend-drogue-dev.apps.wonderful.iot-playground.org/         <Not Set>
bar *     https://console-backend-drogue-dev.apps.wonderful.iot-playground.org/         <Not Set>

and will use "default" as context name when drg login is called without a -c arg. Please vote

15:49:29
@jbtrystram:matrix.orgjbtrystram *

proposal :
I updated drg config list to display the cluster address :

NAME   ADDRESS                                                                                     DEFAULT APP
foo        https://console-backend-drogue-dev.apps.wonderful.iot-playground.org/         <Not Set>
bar *     https://console-backend-drogue-dev.apps.wonderful.iot-playground.org/         <Not Set>

and will use "default" as context name when drg login is called without a -c arg. Please vote

15:49:35
@ctron:matrix.orgctroncan you rename a context?15:50:36
@jbtrystram:matrix.orgjbtrystram drg rename default wonderful.iot-playground.org is already there 15:51:16
@jcrossley3:matrix.orgJim Crossley ctron: you still around? 17:08:05
@freenode_jcrossley3:matrix.orgjcrossley3 left the room.17:50:02
@freenode_jcrossley3:matrix.orgjcrossley3 joined the room.17:53:24
@jcrossley3:matrix.orgJim Crossley so it seems my inability to consume an event off our iot-channel is due to the fact that we're not putting CloudEvents on that iot-channel. the message in the log is a base64-encoded {"temp":42} which is just the raw data published to the http/mqqt endpoints. 19:00:45
@jcrossley3:matrix.orgJim Crossleyanyone see a problem with cloudeventifying those events?19:02:07

There are no newer messages yet.


Back to Room List