Hello. Welcome. Hey, my name is Linsa. I'm the moderator for this session. I work for a small company, Solo.io, with specializing in application networking. We still have some spaces up front if you are brave enough to walk on the first row, second row. So, please welcome, Erin, to present to you a scene that is believing debugging with ephemeral containers. Thank you. Okay. Let's get going here. So, let's see if I can make this work up. Getting a little ahead of myself here. There we go. Make sure PowerPoint is going to do what I need to do. Okay. So, I'm going to be talking about ephemeral containers today, of course. I'm Erin Alpar. I work with Castin, software engineer with Castin. I do software engineering sort of stuff. I primarily focus on the data layer persistence. So, today I'm going to talk about ephemeral containers. So, and what's important about ephemeral containers is that the, they are more than just containers that stick around for just a little while. They are a very important piece to Kubernetes architecture. I'm going to give you a little bit of that and hopefully reasons why, as well as a lot of the technical background that makes ephemeral containers work. And hopefully, by seeing that technical background, you'll get an understanding of what their power is. So, anyhow, so let me proceed. This is going to be a pretty technical presentation. So, I encourage you to download the slides. They're up on schedule for this. I just happened to update them about a half an hour ago. So, if you've already downloaded them, try to download them again. The content remains largely the same. So, the ordering of a few of the slides and I've emphasized some details in the new ones. So, if you're following along, I encourage you, definitely encourage you to download the slides. I've got a lot of console-y type text in here. A couple of slides. The fonts are small. So, I'm hoping that folks can see them yet another reason to download the presentation. Anyhow, let me get started. Before I get started about talking about ephemeral containers, I'm going to talk about what you're going to need in this presentation. This presentation is both me presenting and talking about it, as well as a sort of self-driven tutorial. So, I'll talk about that as we go along. To make this tutorial work, you're going to need, and this is designed to do after the presentation. I don't try to follow along while I'm talking because we've only got 30 minutes since it could go pretty quickly. I'm using kind in this presentation. Kind is a local cluster. The reason why I'm using kind is because I'm going to need direct access to the node and I'll basically need privilege access to the node. So, the easiest way for me to do this is to start up a local cluster. In this case, I'm using kind, which happens to be what Kubernetes uses for their own testing. It's fairly featureful and it will certainly do the trick for our presentation. It does use a docker. So, there's implied that you'll need docker installed to make this work. I think that's pretty standard at this point. I'm also going to be using Postgres. Postgres just happens to be an open source application that I can install with Helm. It doesn't really matter what you use. But the examples I'm going to be using are going to be using Postgres. Okay.  So, and the blue, you see the dollar sign there? That is a command prompt. That's in bold, right next to it. Blue text. That is something you can copy and paste into a shell and you should get output that looks a little bit like the gray text that follows it. So, voila. So, this is my command to create a kind cluster. Just type that in. Kind create cluster. It'll go about its business and create a new local cluster for you. After you've got a new local cluster installed, you can install Helm. So, this is a command to install Helm. I use Bitnami repos. It's in there. Create a namespace for it and then use Helm 3 to install that. At that point, you should kind of be all set. You got kind installed. You got Postgres installed. You might want to check your versions just to make sure that you've got the correct stuff installed. I am running with Bleeding Edge. This is another reason to use kind is that you can get the latest versions of Kubernetes as well as, of course, Kube controls. Be compatible with that. Then I can go ahead, make sure I've got my pods running. Postgres will run with a single pod. Okay. So, you're all set up. So, now for ephemeral containers. So, ephemeral containers are new. They're beta in 1, 2, 3. This means that if you install Kubernetes 123, they will be enabled by default. So, you're not going to have to set any feature gates or anything like that, which is nice. All of the platforms, as far as I know, have 123 on their edge release. So, if you want to play around with ephemeral containers on something like GKE or what have you, either it'll just be installed by default or go take a look at the edge releases and you should be able to find it for installation. It should be fairly straightforward. So, with all this, ephemeral containers start with debugging. These are the cases that you'll primarily see on all the example sites for ephemeral containers and a vast majority of the literature that's out there is about debugging using ephemeral containers. So, I'm going to start with that. I'm going to talk just a little bit about debugging in general in Kubernetes, very high level, and then I'm going to do a deep dive into ephemeral containers and not so much the process of actually debugging your programs, but the stuff that makes debugging work. And I'll get into a few examples. So, there's, again, there's a lot of implications that go far beyond debugging with ephemeral containers. Okay. So, this is debugging by attaching. Hopefully, everybody's familiar with this. This is where you might have a pod that's having problems and you've deployed this pod with, like, a Debian release or maybe even a Red Hat release, and you just shell into it directly and you run commands and try to figure out what's going on. Here's an example of doing that. Ta-da. Kubekettle exec and we just run a bin shell or what have you in the pod so we can go ahead and log in and debug into it. So, you can debug by attach or you can debug by copy, which I'm not sure everybody really knows about, but this is using the actual debug command. It allows you to create a copy of your pod. So, pods are the smallest unit of scheduling. So, with the current infrastructure, what you have to do if you want to run a new process in a pod other than exacting into it is that you're going to have to create a copy of it with a new container or with whatever debugging tools, a new image or whatever debugging tools that you want. So, this is debugging by copy and what this does is it creates a copy of the container and it runs that. It's a little awkward, but it works. If you don't know about it, I encourage you to look it up. So, debugging without a femoral container so we can either attach, which I covered, which we can either copy, which I also covered, but this is a little, if you debug by attaching, you need to include all of your debugging tools in your container so you can attach to it. If you want to change that container to include additional tools, you're going to have to copy it. And this requires doing some foo magic on your workloads to make that work. So, like if you're working with a deployment or you're working with a stateful set, you're going to make a copy of the pod and then the stateful set's going to look at it and see that it's replicas of change and then it's going to start up another pod and you're going to have to set your services to point at the right pod. Anyhow, it's a little bit of a mess, but you can, once you get the hang of it, it works. Ephemeral containers get around this, and I'll talk a little bit about this. This is how you debug by ephemeral containers. So, you've got Kubernetes 1, 2, 3 installed by kind. You've got Postgres in there is my previous example. Copy and paste that command in there and what you get is an ephemeral container. Busy box. Standard set. So, this is a, it actually runs a new container. The pod stays the same, a new container is added to it, which is really handy. This is a little bit of a, a little bit of a special container. It's probably not going to be obvious immediately because all containers within a pod get to share the same network resources. So, so anyhow, by default, you'll see network resources shared. That's, that's really nice. And this is this ideal case for doing more complicated debugging. And as we'll see, we can get really, we can get really complex. We can get really complex with debugging, not just simply network resources. So, here we go again. Here's another example of debugging with ephemeral containers. Again, you can copy and paste this. You see the usual prompts. You know, if you don't see a prompt, hit enter. Now, when you're looking at the pod, the pod resource, the pod spec, things are going to change. So, I want to talk a little bit about what it actually looks like in the pod spec. So, you can see that after you've executed a ephemeral container. And then I'll kind of revisit this and talk about it again later on. So, this is the ephemeral container spec. So, I've run the previous command, boom. And what I get is a new ephemeral container that will be evident in the pod spec. Here's the ephemeral container spec. So, I'm going to go ahead and get the pod as YAML. And down here, I know the second. We have a spec. We have our containers there. And we have a new property, ephemeral containers. This is a zoom in to that. And again, here we see it. So, this lists all of my ephemeral containers for which I have one now. So, that's executing. There's another important part of this.  We also, on the status property, the spec, I also get a ephemeral container entry. So, we get two new entries in the resource, the YAML, for the resource. One is just regular ephemeral containers that tell us what ephemeral containers should be started. And then I have the status end, which gives me the current status of the ephemeral containers. So, I'm set. I can debug with ephemeral containers. I know what to look for on the spec. So, I can see what the status is of ephemeral containers, see which ephemeral containers are running. And again, the spec is changed on the pod as it's running, which is unique. That's one of the things that's really nice about ephemeral containers. But what is a ephemeral container? So, this is actually going to be a majority of the presentation. And I'm going to try to spend some time on this. A container can be thought of as a sandbox, right? So, you're in the sandbox, you're executing commands, and what you can see is limited. You can't see the entire system. You can't see into other pods, right? You can't really see into other containers, actually. You're basically, you're in a container. It can be seen as a sandbox. What makes this work is Linux namespaces. So, now, these are not Kubernetes namespaces. These are Linux namespaces. They've got namespace in the name. They're rather different. So, I'm going to talk about Linux namespaces in this. So, Linux namespaces control container isolation. Linux namespaces are the things that don't allow you to see outside the container into the rest of the system. So, you can play with these namespaces so you can see various parts of other containers. So, it's really nice. And this is really what ephemeral containers are about, is controlling Linux namespaces. I'll talk a little bit about this. There are many namespaces. Here's just a few. Mountpid. These are roughly listed in the order of importance. Mountpid, Net, IPC. There's a bunch of them. There's some resources at the end. I'm going to talk about these and there's some resources at the end, and I'll talk about those too. Each namespace is identified by an iNode. So, these are kind of those funny file system things. So, there's an iNode in the file system. It's a virtual file system that represents these. I'm going to talk about the pid namespace, the mountain namespace, and the net namespace. I think those are probably the ones that you're most worried about. And there's also some quirks in there that you should know about when you start to play around with these. So, as I said before, you're going to need privilege access to the node to make this work. And here's an example of this. So, what I'm doing here is one of my first examples of Linux namespaces is that I'm going to log in to the control plane node. This is basically when you use kind, it is the only node you got by default. And I'm going to take a look at the namespaces for pid1. Pid1, of course, is the net. And I can see those by ls-l slash proc. Everybody should know what slash proc is. One, which is pid1. And then for each process in proc, there's an ns. And under the ns directory, you'll see all the namespaces listed out. Over here, on the left, we've got, or the right, rather, we've got a listing of i-node entries with their corresponding namespaces that they're associated with. So, that is in proc. For the process, under the ns directory, you'll see a bunch of files, and those are all related to namespaces. I can get access to if I have a privilege shell on the node. Here's one of those zoom-ins again. This first entry, by the way, that's going to come up later on.  But these are the namespaces for pid1. So, now, if I, that's from the node perspective, what I can do is I can go in and do the same thing and take a look at my Postgres processes that are running on the node. So, that's, sorry, the previous slide was from the init perspective. This is taking a look at Postgres, which is running in a container within the Kubernetes cluster. So, here, I get my pid for Postgres. I ps it as an example. And then here, what I do is I get all the namespaces for the Postgres. And I can list all of those out. Now, these are the namespaces that the container is actually going to use to run Postgres in. And here's a zoom-in of that as well. The identifiers for this aren't so important. And I'll, we'll see more of this in just a second. So, those are how you see namespaces. You can look in proc. You can see which namespaces are identified with which process. In the example that I had before, we looked at pid1, and then we looked at our Postgres namespaces for our Postgres process. Those will come up in just a second. Looking at them doesn't do you much good. What you really want to be able to do is execute something with a certain set of namespaces set. This is what a command called nsenter does. It allows you to enter a set of namespaces and execute commands as though you were in that namespace. So, when you're in a container, this is really what you're doing is running a shell with nsenter. So, your perspective on the system changes according to what namespaces you'll see. This is an example of running nsenter. I'm here. I'm going to run nsenter in the Postgres namespace specifically for network. So, nsenter dash dash network. And then I give it a namespace file in proc that says start up a command using whatever namespace using the network namespace for whatever Postgres is using. And here I just run sstcp-l just to see what's listening. And here we go. If I want, it's a little tedious to list out all of the namespaces that you want to use. So, there's a shorthand it's called target. Target basically allows you to give it a PID and it will enter the namespace of that process. It's really handy. So, if you have a shell somewhere or you have some sort of command and you want to see the universe from the viewpoint of that process, this is how you do it. You specify target, give it a PID dash dash all and then run your command. So, I'm going to show you what things, what doing this looks like from the node executing a big in a namespace versus what it looks like from the container. So, here's a kubectl exec. Here I'm execging a command in the default container in my pot. So, ps-e, yeah, if I just want to see what the processes are. So, here I go, ps-ef, excuse me, those are the processes, should look familiar. And this is the view that we get if I exec directly into the node and then I do an MS enter, give it a target of my Postgres process and I do a ps-ef, basically the same thing. You'll notice if I switch between these two slides, the output is basically exactly the same. So, this, the NSNR command basically is the same, as I said before, is the same thing as running within a container in a pod. So, this tells you that basically this is essentially the same system that your node uses to build up containers. Okay. So, that's sort of the background. I'll get into some more details. And again, a little bit like that blue, the blue text I was telling you about and entering in that. I'm going to use this comparison technique of moving between slides in a few cases to show you what changes when you do certain commands. So, ephemeral containers. When you start in ephemeral containers, network namespaces shared by default, really handy, there's a bunch of other namespaces that are also shared. This is certainly the most important, I think. You can share other namespaces. So, you can kind of tweak things and change your perspective from the container. So, here's a namespace when debugged by attaching. So, this, I'm going to go directly into the Postgres node and I'm going to go ahead and do an ls-l self NS. So, self, if you haven't heard of that, is just whatever the current process is. So, in the container, I'm just doing a PS. Now, I'm doing this next command is a kubectl debug. So, this is a ephemeral container debug, right? Again, into Postgres. So, before, this is like exacting into the container and running a command. This is starting a ephemeral debug container against the same pod and against the same container. So, here I go ahead and start it. Ephemeral container with an image of a busy box. This will start a, this will start a new container and there it is, defaulting debug container name to debug blah blah blah blah blah. We get the usual thing, press enter. And if I do that same command, I pretty much get the same output, but a few things have changed. So, what I get is I get a set of new namespaces. And what's highlighted in yellow are the namespaces that change. So, when I start a new ephemeral container within the pod, I share all the same resources in that pod with the exception of C groups, my mount, my PID, and my PIDs, right? So, when I PID in my container, I'm going to, when I do an ls-l or something like that, I'm going to see my own set of processes, right? When I look at my mount points or when I look at my file systems, I'm going to see my own files. C groups has to do with permissions. I'll talk about a little bit in a minute. But as you can see, my net, the between the two yellow things right there, my net namespace remains the same. So, when I do like an SS or an IF config or something like that, I'm going to see the same network resources as the rest of the pod would normally see. There's time and not so important. The bottom one for username space is actually pretty important, which means you're going to be sharing the username spaces of the pod. So, the user IDs that you're going to see are going to be the same as what you would get in just all the other containers in the pod. So, this is by default. What I can do is, opposed to just starting up a formal container, the default container, is I can set up a specific target container. So, here we are doing a kube-cuttle debug and I'm specifying a target, postgres. That is basically the same format that you used in NSender, right, dash-dash-target, and you gave it a process. That's kind of what we're doing here. So, notice here that fewer of my namespaces have changed. So, this means I'm sharing more with the original pod. And what's most important is now you're sharing the pid namespace with the pod. Excuse me. You're sharing the pid namespace with a postgres container, which is very helpful. So, all of a sudden when you go into this container, you're going to see all of the same processes that your target container is in your target container. And largely the view of the world through your ephemeral container will look just as if you were logged into that target container postgres. So, ephemeral containers versus kube-cuttle-execing. Kube-cuttle-execing into a pod or into a container, you will basically see all the resources in that container, but you'll be limited by mounts, that is, by the tools that are available in that container. So, the files will change. You will get network namespaces in IPC and UTS and so on and so forth by default, which is great. It's very handy for doing regular network debugging. So, you can share the pid namespace by using target. I'll talk a little bit about that more. So, let me talk a little bit about ephemeral containers and how to get access to more. So, you may want to get access, for example, to file system mounts and a few other things, and I'll talk about that. So, ephemeral containers are a sub-resource. Technically, they're basically a new resource off of pods. It is now a sub-resource. So, if you want to address ephemeral containers using API calls, you're going to have to use sub-resources, which means that you're going to have to use raw or you're going to have to use custom API calls. I talked about this before. Every time you run an ephemeral container, it shows up in the ephemeral container property, and the statuses, the dynamic statuses, exit codes and so on and so forth for those containers is listed in the ephemeral container status. Oh, yes, unique names must be used. I'll talk about that a little bit more in just a second. Here's a handy command for listing out ephemeral containers. I get all my ephemeral containers and I get all my ephemeral container statuses. As I said before, not all properties are available from kook cuddle. You can run kook cuddle exec to start up ephemeral containers, but there are some namespaces that you don't have access to from the command line. There's mounts and mounts, excuse me, mounts, pids and something else not coming to mind, regardless. We'll see that in a second. Oh, yes, you cannot remove or change ephemeral containers or ephemeral container statuses. So, you'll see this once you try to access the sub-resource directly. You can add ephemeral containers. You cannot remove ephemeral containers. Now, remember that every time you start in an ephemeral container, it's added to the ephemeral containers in the pod and the ephemeral container statuses. This means as you start ephemeral containers, the more ephemeral containers you start against the pod, the greater, the longer that list will be of ephemeral containers. So, I'm running a little short on time. I'm almost at the end of the presentation, so I think it's going to work out well. So, this is an example of a custom API call to create an ephemeral container. In my case, I do not have access to volume mounts using the regular kook cuddle debug command line. So, this is an example of how you do that. Since it's a container, you have access to all of the volumes in the pod. So, what I can do here is do a custom API call, create a custom ephemeral container with a mount to create to access my mounts. Now, there's a good reason why ephemeral containers don't allow you just to mount the copy over the mount namespace of the pod is because the proc amount is an important mount and that affects the rest of the system. So, you have to be choosy about which file systems you mount and that's why you can't just go ahead and share the mount namespace.  But regardless, you'll have to pick and choose your mounts. This is one way to do it. This is an example of the once again the comparison of the namespaces between the mount, the, excuse me, the ephemeral container I just started with a new mount. Notice we get a new mount namespace. So, it's basically the same as I had before when I started ephemeral container by default. But I created a brand new namespace so I can mount my volume mount that's in the pod. So, that's useful. Here's taking a look at some of the mounts that I have. There's my new mount slash mount. And I can go ahead and I can list that while the files are there. So, if I can mount, if I can do custom mounts, then I have access to some of the data that's in my pod. Once you do that, you can start talking about doing really interesting debugging. And there's also a privilege mode that allows you to do even more interesting debugging. So, after you've gotten, been able to do your own mounts, been able to get access to the network namespace, be able to get access to the PID namespace. And for some things, getting access to the privilege namespace, which I'll talk about in a second, you can do some very interesting debugging. If you haven't already heard about this, it's called Netshoot. It's a container that's specifically designed for debugging. You can start it up as just a regular container, but its utility is very limited as that. Once you start using it as a federal container, its utility really becomes evident. So, it's a system level diagnostic container. It contains tools like S-trace, L-trace, TCP dump, what have you. It's very nice. So, this is an example of starting up a container using Netshoot as a privilege container. So, I'm skipping a few steps here, but that's okay. So, here, along with my volume mounts, I'm adding a security context and setting privilege to true. So, this is basically running this container as root. Even though the container I'm debugging is not a privilege container, I can run it a federal container as a privilege container. Here, I'm going to run Netshoot, and then when I do that, I can do all sorts of interesting things on my target container that you'd never be able to do in a regular container. In this case, I can run S-trace, for instance. So, I can look at system calls that are executing. I can look at all the network resources. If you've got them out set up, you can take a look at the data that's the changes in data that your target container is making to the file system. So, it gets pretty complete at that point. Here, I'm going to do a similar comparison here. Here's my classic kubectl exec, excuse me. Here's my classic kubectl exec. So, this is from slide 40. This is when I logged in originally to the pod to just see all the namespaces as if you just exact into it. This is the one using my privilege container, debug container 2. There, you see those two new namespaces, the C group namespace and the mount namespace. Take a look at that C group namespace. That happens to be the same namespace as PID 1 in that original example in slide 30. So, C groups control permissions. So, that is the namespace. I think of namespaces as being what you can see in C groups as basically being the dials. So, here, we're sharing the same control as PID 1 basically in that pod. So, that's what a privilege container is for. I see. We're doing good. So, with all of that, given that you can get complete access to your pods through ephemeral containers to the point of having access to basically privilege access, I encourage you to look into C groups. This allows us to talk about distrelis. So, distrelis is when you deploy containers that only contain the application that you're going to want to run. They don't contain any of the utilities. So, with ephemeral containers, you can start to start containers beside your application containers with commands like LS and PS and what have you, and given that you can have up to, you know, this sort of privilege access to the pod, you can then run those commands against the containers just as if you were in the container itself. So, this loosens the requirement that you have all the tools required to debug or even really use your containers in spec files within the containers themselves. So, that is basically it. Here's a list of resources. I encourage you to take a look at these guys. They're fairly valuable and they're pretty comprehensive in terms of C groups, which is the next important topic, which I didn't have time to cover, as well as what makes containers work and some of the intentions behind ephemeral containers beyond simply debugging. So, I'll open it up for questions. I think I've got just a few more minutes. Yeah. Thank you so much, Erin. That was a great explanation. I think we probably have time to take one question. I don't see any questions online. So, I'm going to walk to the gentleman. Hello. I'm just missing a piece from your presentation. What happens to the ephemeral container once you're done debugging? It remains as an entry in the pod. It goes away. You get an exit code. So, the question is, what happens to an ephemeral container once it's done? If you exit an ephemeral container, the entry remains listed in the pod. Nothing you can do about that. You will see an exit status within the ephemeral container status that says whether it exited with a code of one or zero. You can get some log information from it, which is handy. If you opened a terminal to that ephemeral container, if you attempt to attach to it using kubectl attach, you'll actually get the last screen you saw. So, it's kind of a double-edged sword. It allows you to see any errors, last errors that were output. But at the same time, if somebody has access to kubectl attach, they could see some sensitive information that might be listed there. Thank you. Oh, and once you restart the pod, the ephemeral containers will go away and you get to start over from scratch. Okay, with that, let's thank Erin again for a wonderful presentation. Good job.


from Union Square in downtown San Francisco. It's theCUBE, covering PagerDuty Summit 18. Now, here's Jeff Frick. Hey, welcome back, everybody. Jeff Frick here with theCUBE. We're at PagerDuty Summit at the West and St. Francis at Union Square, San Francisco. About a thousand people getting together, talking about the evolution of PagerDuty. We're really excited to have Jennifer Tajada here, the CEO, just coming off a terrific keynote. And I got to say congratulations on your recent round of funding that made all the news a week ago. It's great to see you. Thank you very much. It's great to see you again, as always, Jeff. We love having theCUBE with us at Summit. Thank you. And I have to say, we do hundreds of events over six years I've been doing this. I've never seen a Summit picture in the keynote until the Summit. So you got to work then twice. I love the message really about taking the team to the top of the mountain, that moment of truth. And then you got to just go for it. You got to be prepared. You got to have the team. And at some point in time, you just got to go. It was awesome. Point them down. Yeah. Jump into it. So big topic here before has been kind of dev ops. But you guys are moving beyond that. You're kind of taking this classic play, start as an application, move into a platform space. And you guys know with all these integration announcements, the announcements of BI, the growth obviously, the support from the funding that you just got shows that you guys are well on your way to take what was a pretty special purpose application and take it into a platform play that crosses a whole bunch of other applications. Yeah, I take it even one step further. We almost started out more like a consumer app. I mean, it was really an application built for engineers to make better use of their time on call and frankly not being woken up when they didn't need to be, right? And so everything about our first product was designed around what does a developer need? What does an ops person need? What does that look like, et cetera? As opposed to being designed for the CIO or the CTO or the company, right? And I think that user centricity, that user ethos has served us really well because we start there, that's our starting point. Who's the community that is using our products and services, how is their role changing? How's their world changing and what do they need from us? And that was really the foundation of the trust that we built to start to become truly an ecosystem because all those users started pushing their data to us, their monitoring data from their APM environments or the data from their ticketing platforms or the data from their cloud services. And with that information comes the power to be able to really create context. And now with the aggregation of nearly 10 years of data coming from our responders and how they behave when they're under pressure, the workflows, which ones work better, which ones don't work so well, and the events, the signals that all of technology and the internet of things throws off in real time all the time, you bring that data together and apply machine learning and artificial intelligence to it. And we really are putting ourselves in a position, not only to be the platform that serves a real time business and orchestrates teams as sort of the platform for action, but importantly becomes the trusted engagement for automation or engagement of autonomy for a fast moving business in the future. Right, because you talked about real time and I just want to throw a couple numbers out that you had from the keynote, 3.6 billion events. So it becomes apparent really fast. So far this year. Right, even though people are at the center of that, that's kind of hard to manage. So you have to start to use the intelligence, you have to start to use business intelligence and artificial intelligence to help filter and help that person do their job much better. So you guys are making a lot of plays there and we see it all the time. It's not the BI vendors per se, it's the use of this technology in the background to make apps work better. And it's the fact that not only do we correlate the signals and turn them into intelligent insights, but we can then route those signals intelligently to the right people and orchestrate the actual physical work. So a lot of the technology community has been focused on just that technology and our focus is really on people and teams. How do you empower teams closest to the action, closest to where the proverbial stuff hits the fan at a really exercise restraint there to be in a position to make the best possible decision in those tiny micro moments that matter. And the consumer used to wait maybe six minutes for a website to download. Now, if an app doesn't work perfectly in six seconds, maybe three seconds, you're gone. I walk out of the building in our office in San Francisco and see our employees and they're toggling back and forth between ride sharing apps and food delivery apps and Tinder and whatever else is going on. And it's literally like in a couple of minutes. They're working through eight, nine applications at once. And if any one of those does not work the way it's supposed to, they're done. They just move on and it's one or two times before they'll delete that. So the technology community is now responsible for delivering the perfect brand experience digitally every time and they've got to be empowered to do that with the right tools and services. And the expectation is set by the best. I mean, that's the funny thing, right? What was the best or cutting edge quickly becomes the expected norm? What is the most delightful thing that ever happened to me? Well, that's what I want from you. I mean, that is basically the way it works. And you talked about trust and trust is such an important part because one of the key pieces that you guys are enabling you talked about in your keynote is letting the person at the frontline in that moment of decision have the tools and the data and the authority to make the right call. And it's not a escalation up the food chain, wait, send some emails. It's really empowering that individual to get the right thing done. And that's a core tenant of DevOps culture. It's actually born and agile in fact, but what's really interesting about it is it's the way companies need to be run now. If page or duty waited for me to make every big decision, we would be back where we were three years ago, right? And as a result of being able to empower our teams, great information, very clear understanding of our goals and the time frames that we expect to achieve those goals and then context as we progress through our journey to understand how we're doing against those goals, it gives them the power and the intelligence to make better decisions every moment when I obviously can't be there or their leadership can't be there. And in fact, it means that the most important decisions are getting made where the person's closest to our end customer, the user. And that makes a ton of sense to me even if it's not the way I was taught leadership or taught to manage.  So every time in me, I look up at you, I look at Australia last time I saw you speak at the Girls in Tech thing, so this is great. Another thing that you acknowledge in your keynote I wanted to get into is that tech and people are imperfect, right? They are imperfect and that's kind of part of what the DevOps ethos is, is that that's okay, we're just going to make it better today than it was yesterday. And I think Ray Kurzweiler's keynote about exponential growth and just the power of compounding which so many people miss out on. So that's really where you're trying to help people solve problems. It isn't the big Eureka moment. It's how do we learn? How do we get better? How do we make improvements? Well, and a lot of people in the Valley talk about failing fast. In order for failing fast to have a benefit for a company, you not only have to be allowed to fail, it has to be okay when you fail and there has to be an open, transparent conversation about what you learned, what went wrong. And that has to be a blameless, high empathy discussion or it doesn't work. If someone thinks they're going to get fired by marching you through all the details of their failure they're never going to tell you the truth. So when we think about incidences they come up or something breaking, not working the way it's supposed to or a business initiative, not, you know, turning out the way we thought it would, there has to be a blameless conversation so that everybody in that community learns so that we're better the next time around and that's where the compounding benefits come. Right, right. To the whole team effect. I thought the quote, I've never seen that quote that you brought up today. Teamwork remains the ultimate competitive advantage because it's both so powerful and so rare. That is a really scary statement but we see it all the time. In fact, I was at another keynote and there was a behaviorist talking about how do we get everybody pulling in the same direction and John also talked about that in terms of incident post-mortems and how do you make sure that you're learning and not just filing reports. So you guys are right in the middle of that. I thought John captured it really well when he said it's not about the technology we spend all of our time monitoring and talking about the technology, it's about us and it's us that actually makes this technology great and applies it so effectively to problems and challenges and opportunities in our world and in our lives. But what is also interesting is Patrick, what's also interesting is Patrick Lanzioni's paradigm around the first team. So most employees come into a business and they think the most important world for me in this company is my team, the people in the team who I report to, you know, a leader and it's just us or for leaders they say it's just the team that reports into me. Your first team is your peer group. Your first team is that and by first team I mean the most important highest priority aligned organism that is gonna drive massive change in a business. It's your peer group. It's the people who work across functions to help reduce friction in a business and drive fast outcomes and great results, right? But most people naturally kind of hunker down into their core team and that's the beginning of the silo mentality, right? And so one of the things I love about Patrick's book and you're gonna hear about that tomorrow on stage is this idea of what it takes to be an ideal team player, to be humble, to be hungry, like good is never good enough and to be smart, to like constantly be learning, to really care deeply about how you continue to push the envelope to get better. Right, so I wanna switch gears a little bit from the people and the individual teams to the ecosystem, right? You got a ton of partners here at the show and you talked about in the keynote, 300 integrations. And I think some people might be confused, right? Because it's always this wrestle for whose screen am I working on when I'm doing my daily job. But as you said, we're in a lot of different screens, right? And I'm going back from Salesforce. I'm in my G Suite. Maybe I'm jumping into Hootsuite for some social stuff. You guys have basically embraced the ecosystem for all these different types of systems and really kind of plugged into that. So I wonder if you could explain a little bit more because I'm sure most people might be confused by that. You know, I sort of think of us in the same way I would think of like the brain of an Olympic athlete, right?  But the brain has to accept the signals from all the different parts of the body and then work through them, correlate them and then drive action, right? And I sort of think of major duty as sitting at the center of this, you know, rapidly changing technology ecosystem, this live organism, and really understanding the signals no matter what the, is it raining? Is there a pothole in the ground, you know, et cetera? And being able to then drive change in the process on the fly to help the body perform more effectively.  So being central to the ecosystem is about being neutral and agnostic and really demonstrating you will not only say you will partner but investing in those partnerships. So we build first class integrations to companies that may see us as competition if that's what our customers need. Right, because like you said, it's got to be customer centric first. And it's an open ecosystem and this is what developers and, you know, employees and tech workers expect. Right. And to your point, the amount of data that's flowing through that nervous system is only getting more and the amount of noise to get through to the signal to take the right action is not getting any easier, right? All right, Jennifer. Well, thanks again for having us. Congratulations on the funding and the great show and it's always great to catch up. Thank you. I have the best job in the world. I feel very lucky. All right. Great to see you, Jeff. Thank you. All right, she's Jennifer Todd. I'm Jeff Frick. You're watching theCUBE. We're at PagerDuty Summit where they actually show summits on the keynote screen. Thanks for watching. We'll see you next time.


Hello everyone, my name is Amit Dam of Adon Journal. Today, I will talk about the Scotia Bank Gold American Express Credit Card. The Scotia Bank Gold American Express Credit Card is a travel rewards card that lets you earn a Scotia Rewards point for everyday purchases that can be used towards eligible travel costs without any restrictions. The card comes with a $99 annual fee, each additional card costs $29, the minimum annual income required is $12,000. You get 20,000 bonus points if you spend $500 within the first 3 months which is valued at $200 and there is no anniversary bonus. You earn 4 points per dollar at eligible gas, grocery and on dining and entertainment in Canada. For everything else, you earn 1 point. Let's go over with some of the features this card offers. You can book with your travel provider and reading points for your complete trip including taxes and fees. Access to 20% off and complimentary upgrade on hotel booking if available. Low price airfare alert will monitor your itinerary and if your lower price becomes available, the agency of record will automatically change your ticket for the lower price. Access to 24-7 full service travel agency, access to 24-7 concierge services, 35% discount on priority pass annual airport lounge membership and much more. The Scotia Bank Gold American Express Reward Credit Card comes with all insurance benefits you can possibly think of. Emergency medical insurance, travel accident insurance, auto rental insurance, trip cancellation insurance, trip interruption insurance, flight delay insurance, lost and delayed baggage insurance, hotel motor burglary insurance, extended warranty insurance, price protection insurance and purchase security. For a low $99 annual fee, the Scotia Bank Gold American Express Card comes with so many features and benefits that is very hard to complain about this card. For example, if you look at the regular American Express Gold Credit Card which charges $150 annually but it doesn't provide any concierge service or it doesn't provide trip cancellation insurance. The only thing I can complain about the Scotia Bank Gold American Express Credit Card is that although it is a travel reverse card, it doesn't provide 4 points on travel purchases. For example, it provides only one point on travel expenses. Another thing you need to keep in mind is that Scotia Bank American Express Gold is an American Express blended credit card that means it will only work on American Express Network and you might be limited to use your credit card everywhere else like Visa and MasterCard. Finally, a point worth mentioning is that the insurance services provided by American Bankers Insurance Company Florida and like Alliance Global Insurance which provides travel insurance for many Canadian travel viewers credit cards, for example, BMO World Elite MasterCard. If you search online, there are numerous complaints and bad reviews about these insurance companies. So all these benefits would look good on paper but what good would it be if you're having hard time or unable to process your claims. I'm much more comfortable dealing with insurance companies like TD, RBC, American Express and so on. So before picking any travel viewers credit card, make your call. As of this writing, I do not hold this card. That's all for today. Thank you.


What's up, everyone? It's Takedown here. Welcome back to another video. Today, we're going to be talking about future American NHL expansion teams. Let's get right into this. With the success of teams such as the Vegas Golden Knights and the Seattle Kraken, it's no surprise that there is talks about more expansion teams in the NHL. So let's take a look at some cities that could potentially be home to a new NHL team. First up, we have Houston, Texas. This city is the fourth largest in the United States and has a thriving sports scene. Even with Texas already having the Dallas Stars, they definitely can support a second team. With the city already hosting NBA's Houston Rockets, it wouldn't be a stretch to imagine the city hosting a NHL team in the future. Plus, adding another southern team would definitely add some diversity to the league's coverage. Next, we do have Portland, Oregon. This specific northwest city is known for its passion for sports and could realistically easily support an NHL team. The city already hosts the Portland Winter Hawks for the Western Hockey League, so it wouldn't be a stretch to imagine an NHL team calling Portland home. Lastly, we do have Salt Lake City, Utah. Although it's not as big as the previous two cities, Salt Lake City has shown in the past that it can support a professional sports team. The Utah Jazz of the NBA have been in the city for over four decades and have a passionate fan base. An NHL team in Salt Lake City would not only add to the diversity of the league's location, but also bring a lot of revenue to the city. Now, these are just a few of the cities that could potentially have a new NHL team in the United States. We are excited to see what the future holds for the league and can't wait to see what new American cities will join the action. Comment down below what other cities in the United States you think are going to have an NHL expansion team in the near future. These are some of my picks, but obviously there is a lot of other cities that could potentially see an NHL team in the future or also a relocation of other teams to a different city in the future as well. Hope you guys enjoyed this video. See you guys in the next one. Please take care. Peace.


The following is a presentation of TFNN. The Tiger Technician Hour with your host, Basil Chapman. Call now toll free at 1-877-927-6648 internationally at<PHONE_NUMBER>. Now, Basil Chapman. Hi, folks, we're back. This is the Tiger Technician Hour<PHONE_NUMBER>. And when we're looking at the market, that gap up on Friday was really quite an important thing because it got the cues and the SMHs and even the S&P so close to areas that I had said before were getting into resistance area, but getting to all-time highs is really an incredible thing. But when it happens in a V-shaped pattern, you've got to get maybe just a little pullback and then it almost immediately, maybe in daily charts, it wouldn't be more than three days. I'd say a week would be too long if it was too deep, but if it's just sideways. And then it needs to break out because you want that V-shaped pattern. V-shaped patterns are far more power-intensive than the cup. Why? Because in the cup, you keep having a little bit of a stall and then you move up, a little stall and you move up, and you keep making these higher level areas of support. But at the same time, you're usurping a lot of energy to do that. In a V-shaped, it means you've got such torque, such dynamic thrust to the upside that until you get to a point where you just hammer at a, let's just do this right now, let's look at the XLK, where you hammer against all-time high resistance levels and then it means that you need, especially in this case here, you've got the XLK, the S&P Select Tiger Spider Fund going in two legs. It's almost impossible to describe. There are very few examples of this in two legs from the low of 57.57 in the XLK, back on 26th of December, the week of the 26th of December, 57.57, a 24% decline from the 76.27 October high, and all of a sudden you're looking at, it did take a little longer, not very much. It took one, two, three, four weeks longer. No, sorry, three weeks longer to break above it. But it's only at this tiny little one week peak. It's incredible. Just below the top at 75.25, one point away from the all-time high, it pulls back for a week. This is what I'm talking about. You need speed with this V-shaped thrust. And then the momentum of the MACD hasn't even started its decline. It is still expanding. The histogram is still expanding. Only here in this last week did you see the slightest dip in the percentage. This is the 0% line. That's the distance between the faster moving average, the green line of the MACD and the slow line. But it was very slight. This week, I'm suspecting you will see more of it. Why? We've gotten to a recycled leg D in the XLK. This last move up just made a peak D, another peak D in the 120-minute chart. And this is, if you look at my work over here, this is the Chapman Wave Automated Projections of Resistance and Support, 76, 78 in the daily, 77.04 in the daily, 77, 87. We're in this cluster of resistances. If there is a spiral above 78.50, that's not just a breakout. That is not only going to all-time highs. That's basically saying, you know what? There is so much strength here that it's going to maybe be just a sideways rectangle movement. It finally has a decline. But at this particular point, you could come back to the 75. What was that 75? 25, high of the 21st of March, and that'll be the big test. Does it break under? Does it go to the low of 70? What was that 2? Yep, 72.34 on the 27th. What does it go lower than that? So this is going to be very important. If you're looking at the 120-minute chart, it broke above 76.82. It's not there now, but it did that already this morning. But that is a resistance level. And the 10-minute chart says there were no resistances above. 76.59 was the resistance. Now, some kind of a support we've taken that out. 76.22 is key support short term. I don't have any support levels at all in any of the indices. And the weekly chart has broken out. It's above its 75s resistance. And the XLK monthly chart is at 84.75 all-time. And now, sorry, 84.75 upside monthly target as resistance. Let me just check here. There's a question. Just a little feedback. When you do the updated noon hard to follow everything so fast, could you maybe only do the three major indexes and then get into the rest slower? Thanks, Bezos, for what you do. I will try to do that. And I have a way that I was thinking that I would do it. You've just confirmed for me that it's a lot of information. But you know, people may be listening. TFN is all around the world. So people might just be listening to be able to go on a little bit of a brief summation of what's going on right now. So those are the levels that I would do. As far as the charts are concerned, I have my whole show in which to do the charts. I'll have to think it through. There's a compromise between the two. Some people really just want to get, what's the news? And that's what we do at TFN. And then we give you the why's and wherefores based on our own methodology. Okay, let's do a couple of things here. I wanted to look at the couple of questions that have come in. I will get to them. Oh, I see something here, big heading. It says, Bonds. Ah, good old Paul with his very subtle way of asking questions. Bonds are now putting in a head and shoulders top. So let me go to the Bonds, head and shoulders. I don't know, he never talks about what time frame, since it's never clear. But let me go maybe some monthly. Head and shoulders upside down, round side out, inside way. Head and shoulders. All right, let's just go on with the question. What head and shoulders? All right. There's definitely a Chapman wave, right shoulder failure pattern. That's the H pattern. The dreaded H went under it. Bonds are now up 530 seconds at 142 and 230 seconds. Doesn't look very good. Shorted to a monthly charge only in a C. Probably should go to a D at some point going on. And it could be a major top. You probably won't mention this because you don't understand bonds. You know, Paul, that's not really a very good and accurate summation and implication. I actually understand bonds very well. But I'm not quite sure what the implication there is. So I just want to clarify it when it comes to bonds. I actually understand them pretty well. And question to the Denny Basil, why engage this person? I take every call because I think every call has a particular reason. Someone's taking the trouble to write. It might be not necessarily particularly eloquent, but it's still worth perusing and looking at. It takes me to an area that I might have overlooked. And now that I'm looking at it, there's really not much to say. I see that the yields are stuck in a range for now. And there's really not too much to discuss. Look, TNX is trading in a leg D right now. I said that I can see it maybe going between 25 and half, maybe even 26, and the support of 2356 is imperative to hold on the shorter term. I haven't really changed that opinion. I'll be right back. Now it's done. 85 S&P is done. The TAS Profile Scanner is the most revolutionary piece of trading software that you will ever try. Wouldn't you like to approach the markets with confidence? As you begin your trading day, it's likely that you'll be faced with lots of decisions. In order to make the best decision, the first thing you'll need is a strategy that will help you minimize your risks. Whether we're in a bull or bear market, a good strategy is to have the tools needed to help you scan and analyze the markets before you trade. The TAS Profile Scanner instantly scans and filters over 2,500 global financial markets, such as stocks, ETFs, commodity futures, and forex. Headed by Steve Dahl, president of TAS Market Profile, the TAS Profile Scanner understands that in today's technological world, the use of top-flight software applications, automated trading algorithms, and technical analysis expertise is essential to successful trading in today's market. Whether you're looking at the trade matrix, the ETF heat grid, the market breadth, the landscape charts, or the many other features of the TAS Profile Scanner, this is a piece of software that will revolutionize how you look at the markets and set up your trades. The team at TAS has even put together a 12-part video series to walk you through every aspect of the TAS Profile Scanner, which you can find directly on the TAS Order page at TFNN.com. Sign up now for only $97 a month with a risk-free 30-day trial so you have nothing to lose and everything to gain. See for yourself how you can harness the full power of the TAS Profile Scanner by visiting the front page of TFNN.com today, and you'll find the TAS Profile Scanner under the Services section. Remember, with a 30-day money-back guarantee, you have nothing to lose. Don't let another day pass you by without trying out this amazing piece of software that will revolutionize how you look at the market and how you place trades. Sign up today. TFNN has launched our brand-new website. You can still visit us at the same TFNN.com URL, but when you do, you'll see a new and improved TAS Profile Scanner at TFNN.com. Sign up now for only $97 a month with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time with a risk-free 30-day time eight internationally at<PHONE_NUMBER>. Hi folks, we're back. And you know, this is going to be very interesting. Look, the IYT, I should mention that we are still along the IYT and I shouldn't have typed it in the 10. I should type it into the chart. There we go. Trading at 194.42 down at $1.94. That's a big pullback. But there was a big gap from the close on Thursday into the Friday leap to the upside. I have this as a leg C. It's still a leg C because we went from 196.36 to 196.45 this morning. And now pulling back sharply. This is going to be quite important for a number of reasons. Just as we're looking, I'm going to mix things up a little bit, give me a little time, with XLF spikes up on Friday with a really good news on J.P. Morgan. WFC Wells Fargo was not as good. Today we've got Goldman Sachs sharply lower and XLF is down 19 cents at 26.95. I would consider that this is really positive action in the XLF. I'm not saying, oh, it's positive. Therefore it's going to the all-time highs. What I'm saying is that under the circumstances of yields, et cetera, under the circumstances of the financial sector, we remember it's a sector, because we've got Berkshire Hathaway. I mean, it's called the financial, but really it's got some companies that have some financials, but that's not what they do mostly. But if you're looking at this and you say, hey, the financials have had a move from 30.33 down to the most recent low of 22. Eight points, that's 28% to 34%. That's a big move down. But all of a sudden, you're looking at some residual strength in the chart since the high of the, the bounce up to the March of, high of the 19th of 2710, down to the most recent pullback of the 25s. There's that noontime sneeze, I guess. Well, what we're looking at, it's gone to a new leg B. I'm calling it a leg B. And I'm anticipating that there's a chance. It might take a little while, but as long as the 2638 level of the 200-period moving area, it's this area, it might go a little lower. I would not like to see it under 2610. But if this can hold, and just maybe for a little bit of the gap and then have a little bounce later in the week, thank you. Then I'd be looking at and saying, well, a very quick peak A to a peak B to a leg C says be careful because, yes, you could go to the leg D and then you could get a pullback. Now, the rule of the Chapman wave is a very quick A to B to C. This is peak A, peak B, peak C. And then to a D, usually it's the B to C to D. A takes a little bit of time and then has a bit more of a rest. That says that it could have a sharp pullback, but it doesn't say, oh my God, that's the end of the move. It's going all the way back down. It just says be careful because now it invariably will have a bit of a rest. And that rest is either time or price or time and price. I'm thinking that it's more time and less price. This is just at this particular point. Why? Well, let's look. You remember I was talking about the IYT. That's the transport. So the reason why I went over to the XLF is because I wanted to show that within sectors there are conflicting chart formations. In the IYT you've got the rails that have been doing very well. Got some trackers good, some trackers not so good, but you've also got the airlines which are being pummeled. So I want you to show you that the same sort of things happen in the XLF. Now watch this, this is really quite fascinating. Within the XLF you've got Goldman Sachs down sharply, down three and a quarter percent of 201.16 having made a peak D on Friday. This is an island reversal. I'm putting this in. I suspect this island reversal won't remain an island reversal for all that long, but right now it's important. But if you look at the weekly chart you've got this Chapman wave oval pattern is going to peak A then a B, and then it took some time and then went to a C and then a D. But the high from the 202 area, the 207, 208-ish area, that took, look how much time it's taking. It's taking a couple of months. Number one. Number two is in this particular pattern you've just gone above the oval high. This could start to set up a pullback that says we're using up time. This is big rectangle formation. You might have to test the 198 area, even the 196s, but there is a really good chance that when the assessment of Goldman Sachs et cetera has actually been accomplished that the XLF based on, now you've got earnings tomorrow from who else was there today? Goldman Sachs and someone else, someone important. Goldman Sachs and someone tell me, someone tell me. There was another, oh, city, I'm sure it's city. Yep, city's down 31 cents down .46% at 67.11. It has gone to the resistance level that I drew in the other day when I was talking about it. This is also an idea, very quick ABCD in the weekly chart. It could have a bit of a pullback but I have to tell you both of these stocks are holding really well right now. I'm kind of impressed at what they're doing. So the day is young, the week is young. We've got other bank stocks coming up, Bank of America which we are long, pulling back today down 152%, 1.5%, 47 cents lower, 29.71. Really nice move when right in the Chapman wave right there, resistance zone. This is the area that I call inside track, repellent, resistance level, pulling back from there and it's good for the gap. I think at Bank of America it's important. What if two scenarios, what if Bank of America which is I think just based on the techniques that are the prerequisites that all the banks have to have, all the different things that they have to do to conform to whatever has been committed by the Fed that says they've got to have this and they've got to have that, they've got to have security, they've got to have X amount of capital, et cetera, all these reserves, et cetera. But wait a minute, what if Bank of America instead of pulling back to the 29, 20, 2902 level of nine and the 14 period moving average by tomorrow has an outlook that is actually a little bit better. So what they say is the earnings are okay but the outlook is we've done everything and the outlook for this next half should be better or the other way around. The earnings are a little disappointing. No, the earnings are very strong but they're a little timid in the outlook. When that settles, if the earnings are strong that should really help the stock. Now let's just imagine over the next two days whatever the reason, that Bank of America instead of trading in the 29, 30 to 29, 20 area down another 50 cents or more, tomorrow has a kind of a sort of a stumble at first and then out in the blue by the end of the day is climbing, climbing, climbing. And by Wednesday it's above the 30.22 high of the 12th, starting to exceed. And by Thursday without making a peak it breaks above this resistance, inside track green dash green line and starts to trade in the 30.45, 30, 30.50 area. You know what you realize? What that would do, that would say that Bank of America with this megaphone pattern in the weekly chart has broken to the upside rather than starting to make this deadly diamond pattern which always breaks to the upside rather than be deadly. But instead right now it extends leg C and all of a sudden the 31.92 high of the 10th of March becomes a magnet. So I'm looking at this and I'm saying there are numbers here that are really important for me because in Bank of America close below 29.40 he says, all right be ready for some kind of sideways pullback but breaking out is really good. I'll be back down. Since 1984, Basil Chapman has been using the Chapman wave methodology to advise traders of his expert market opinion. While originally hand drawing charts from the late 1970s into the 1980s, Basil noticed that prices under most circumstances virtually always had a certain number of legs to the upside before declining sharply. Later Basil found that computer software which included the standard market technical indicators enhanced the degree of accuracy in calling price turns as well as market trend calls. Thus was born the Chapman wave sequence. Using the Chapman wave methodology along with other indicators, Basil Chapman advises his subscribers of his expert market opinion each market day with his opening call newsletter. Right now you can get a two week free trial to the opening call, Basil's daily trading newsletter by visiting the front page of TFNN.com. Cancel at any time during that trial and pay absolutely nothing. Get your two week free trial to Basil's newsletter, the opening call today by visiting TFNN.com. The path of least resistance is David White's daily trading newsletter and if you're looking for active trading ideas then now's a perfect time for a 30 day free trial to this powerful daily trading advisory service. David uses his years of trading experience to offer his subscribers his trading ideas each morning in his path of least resistance newsletter. Using a combination of equity trades along with options, David keeps his subscribers up to date with all pertinent market information with intraday afternoon updates when warranted. Don't miss out on this great chance to get a 30 day free trial to David's daily newsletter, the path of least resistance with no obligation to pay anything. David has been delivering solid recommendations for his subscribers recently and if you'd like to see the type of newsletter he delivers every morning then visit the front page of TFNN and you'll find the path of least resistance under trading newsletters. For all the details and to start your 30 day free trial today, log on to TFNN.com now. TFNN is excited about our new software charting program, the Art of Timing the Trade Charts. In collaboration with Tom O'Brien and using his best selling book, The Art of Timing the Trade, your ultimate trading mastery system, David White has programmed an outstanding piece of software that will complement any trader's methodology. Using this first of its kind program, the Art of Timing the Trade Charts allows you to scan thousands of stocks for Fibonacci formation setups, including guardleafs, ABCs, butterflies and much more. The Art of Timing the Trade Charts is designed to help you when scouring the markets for stocks just beginning to form the trading patterns that many investors spend days, weeks or even months searching to find. And right now we're offering licenses available at only $79 a month. We are so confident that you're gonna love this new charting software that will even give you a 30 day unconditional money back guarantee. Don't miss out on this incredible new piece of software. Get your copy of The Art of Timing the Trade Charts today by visiting TFNN.com. This segment is brought to you by Think or Swim. For more information, just click the Think or Swim banner on the front page of TFNN.com. Okay, so the question with the bonds was about a head and shoulders and I've done, I do see a potential for inverse head and shoulders, but so far I don't see much else. All right, so the DSX is a question. DSX is called Diana Shipping Inc. Trading at 3.13. It hit a low in the 2.40 area just in mid-March. Very nice action leg A in the weekly chart. So the little joke was, let's see, what was the joke? Oh, there it is. Basil, you probably don't understand shipping, but can you take a look at DSX for me? Thanks. Yeah, I don't understand shipping at all. That's why we just missed LPG, Darian LPG, liquefied gas shipping from the 5.50 area, which just happened to hit 8.35. Yeah, so good one. So we're looking at the DSX, DSX is Diana Shipping. Nat was the one that I had spoken about for subscribers as well sometime ago. We'll look at that in a moment. Yes, this is very good. This is a really good sign for the economy. This is a very subtle sign because it has to do with dry shipping. LPG was natural, it was gas, that was being shipped. So this is gonna be very important, 3.13. If this is just a leg A to the upside in the weekly chart and at some point we're gonna pull back and then make a leg B, it says that the 2.50 to 2.80 area is probably gonna be really good support and this is just some horrible news that comes out and that maybe the shippers are starting to move stuff that just was sitting there for quite a while. Let's look at NAT. This is Nordic American tankers. Yeah, she also had a very nice move from the 180s. It hit 210s, now straightening to 206. It's a start. This is not as good as the pattern that you have in DSX, which is Diana Shipping. So yeah, I like it very much. So Peter says, the bells are she's running through Newton, as you speak. We got a dinner, a tiger whose wife is running a marathon. She often runs the marathon. I think she didn't do it last year and she's going right by my city, Newton, as we speak. Probably just about to go to Heartbreak Hill. Oh man, that's Heartbreak Hill. I remember when I used to bike it, I'm not big on bikes. I mean, upheals on bikes, I haven't. I'm very good at down here, like everybody. Okay, so I wish her the best of luck because this is now a beautiful, maybe it's getting too warm, but this morning, the storms here in Boston, you would not believe it was, I've never seen this before. I've seen rain last year was rain and cold. This is, there was torrential and wind-blown storms this morning at about seven o'clock. Just absolutely, I mean, I went out just for a brief moment and I was soaked. And what I am looking at is a situation where that just lightning, thunder, heavy rain, and now it is absolutely spectacular outside and warm. So maybe it's getting too warm, but I personally prefer before warm, too cold. So I wish her the best of luck and it's been quite, I only saw a little bit of it. I used to be able to just, in the old days, I could just zip down the hill and go like not even a half a mile, just like a quarter of a mile to Commonwealth Avenue. I would just stand there for a little while, watching everything and then come back to the market to marvelous and go back to the market. Now they've got cops at the bottom of the hill. You can't go there unless you're biking or walking. It's unbelievable, but it's really a big fundraiser, a huge fundraiser. However, the level of the Boston Marathon has gone to such a, not everybody gets in, just I have to congratulate her to get in. People have to work really hard. I heard of someone yesterday who missed getting in by one minute, but then the cutoff was three hours and 83 hours, one minute. They have to come back next year. So congratulations, I'll tell the story. Way back when I lived in the back bay, I had a school holiday when I was at the Nuremberg Conservatory of Music. There was, April, whatever day this is, it was a, for some reason it was a holiday, a school holiday. I can't remember the reason why. Anyway, I was standing, it was a hot day, April, and it was a hot day in Boston. I remember standing in a little t-shirt and shorts and a corner of Nuremberg and Exeter, and Fairfield, sorry. And the next thing I see is a bunch of people running by me and I was an athlete in my youth back in my high school days. I held records and stuff, but for sprinting. And I'm looking at these people and they're running by me and they look pretty serious. And a cop was nearby saying, what's going on? He says, the Boston Marathon. There were no people. They were just running along between the people on the sidewalk and the street. And it was just, there was a right by the John Hancock. It wasn't, it was the Prudential when they used to finish at the Prudential before they finished about 100 yards further down at the John Hancock. And it was nothing, there was nothing there. And now there are 30, 40,000 runners and I don't know how they all get in. It's just incredible. I'm impressed. And I've always been impressed at long distance runners. I just could never do it. 440, I could, I did 440, but it was in the relay where I was the last runner in the 110, the last 110. But I could never do anything more than 220 was my limit. For 200 meters. All right, let's get back to the story. Natural, Nordic Americans are DSX. Yes, I like it. And I like, I think the group is telling us that it's very important that they are running right now. Boston Globe this morning had one of the first stories on the front page that I can recall seeing. And I just don't know how long. What was it? It was about wages have improved to the point where some of the companies are thinking from 15, they're gonna make $20 the minimum. You never saw that in the globe ever. And of course, there isn't one word about this administration helping to do that, but it was a very interesting article on people who are earning more, feeding it more in their pockets and are able to do things that they've wanted to do before. Great story. All right, dows down 67, S&P's down seven. Want to show you something that I thought was interesting. And the many charts that I sent out over the weekend folks, I forgot to do my dows three time frames. I had it already way back on Saturday and I forgot to post it because there were so many other charts. I did discuss it, but I forgot to post it. I sent it off on a special this morning. It came after the opening call went out with all the different positions we have. Just sorry about that. Now what I am looking at is Victor in Paramus, New Jersey. Victor, how are you? Good, how are you doing? I see that Carlos is making a 50% retracement. So do you buy it? And another thing, I just want to let you know the Japan banking system is closed from April 27th until May 6th. Will it have any effect on the market? That's my second question. Whoa, whoa, whoa, who closes? The Japan stock market closes. Oh, yeah, that's right, yeah. They do that, you know, every year they do that, but I've never known it to have any impact other than if at that point the market is going down, it will just still keep going down and if it's going up. So I don't, to tell you the truth, I think the implications of China, just at this particular moment have a lot more import than Japan, but it's very interesting. I was looking at the NK on the continuous contract last night, leg E in the daily, in the weekly charts, gone to a leg C in the monthly chart, is a leg A and what it's done is, unlike our markets, it's had about a 50% retracement. Can you hold on, I look at Kronos because I do want to do some work there because it's impacting a lot of the area. This is the cannabis sector. We'll be right back with Victor Paramus, New Jersey. We're looking at the cannabis sector with Kronos Group as one of the ones we want to discuss. If you're in the CD market and looking for a secure investment, the Tiger First Mortgage Program may work for you. The security for these first mortgages are building lots in the Tax Opportunity Zone in St. Petersburg, Florida. The Tax Act of 2018 set up tax-free zones across the country where you can build and hold for 10 years and pay no tax on the profits, which makes these lots valuable. The investment is anywhere from $30,000 to $75,000. The interest paid is 7% yearly paid on a monthly basis. According to bankrate.com, the best rate for a four-year CD in the country as of February 20th is 3.1%. A $50,000 investment at a normal four-year CD rate of 3.1% would give you income of $1,550 per year or $6,200 over the four-year period. That same $50,000 investment in the Tiger First Mortgage Program would give you $3,500 per year or $14,000 over the four years. What should you prefer? $6,200 or $14,000 of interest on your investment. If you'd like more information about the Tiger First Mortgage Program, you can call me at<PHONE_NUMBER>. That's<PHONE_NUMBER>. It's amazing to think that Tom O'Brien started his weekly gold report 17 years ago with the first issue published April 7th, 2002, when gold was trading at under $300 per ounce. Gold peaked at more than $1,900 in 2011, and after spending many years consolidating at lower prices, gold may be poised for its next big run. Tom O'Brien publishes his weekly gold report every Monday morning for subscribers consisting of coverage of the XAU, HUI, GDX, the dollar, bonds, South African RAND, as well as 25 different mining equities with specific buy-sell recommendations. As of April 1st of this year, the gold report currently has eight active positions with an average unrealized profit of almost 8% for each open trade. New subscribers get a 30-day money-back guarantee so you have nothing to risk. For all the details and to start your gold report subscription today, visit the front page of TFNN.com.  Sign up today. Are China A shares hot or not? If you trade China A shares, now may be time to take a closer look. Trade CHAU or CHAD, Directions Daily CSI 300 China A Share Bull and Bear ETFs. China A shares in either direction. Visit DirectionInvestments.com today. An investor should consider the investment objectives, risks, charges and expenses of the direction shares carefully before investing. The prospectus and summary prospectus contain this and other information about direction shares. To obtain a prospectus or summary prospectus, please contact Direction Shares at<PHONE_NUMBER>. The prospectus or summary prospectus should be read carefully before investing. An investment in the funds is subject to risk, including the possible loss of principal. The funds are designed to be utilized only by sophisticated investors such as traders and active investors. Distributor, Four Side Fund Services, LLC. Don't forget, you can listen to TFNN live on your mobile device 24 hours per day. Go to TFNN.com and hit Watch Tiger TV. That's TFNN.com and hit Watch Tiger TV for the latest market information. Hi folks, we're back. So we're looking at Cronus. Cronus is one of the real leaders. This is a Cronus Group cannabis sector. It has a low back in 2016 and the pennies, I think it was. 0.17, 0.17 has a little bit of 1,000%. Is that 1,000 or 10,000% run? To 25, no, yeah, to 2510, not bad. But now it's on its way down. And one of the things I'm a little concerned about is that there was just, how can I put it? There were certain stocks that were at first benchmarks for the move up. Then what happened is that on every pullback, some of them failed to rally to the next step but Cronus didn't, it continued in. Look at the big U-shaped patterns it made. Every time it ran, look, it went to Leg C in the month, it goes all the way to about 11 and then it pulls back to the fives. It's cut in half, more than half. And then it runs where? To the 12 area, then it comes back to the sixes. And then it runs where? All the way to 25 and now it's getting cut in half. It's down 15, not quite half yet. So my suspicion is that it needs to test the high that was made back in the week of the 21st of September, 15.30 is really going to be key. My suspicion is it's going to go kind of into that area. And then we might find that there's a sudden V-shaped balance but my suspicion is it's going to take a little, there's something going on here that suggests to me, now if you don't mind, I'm going to go CGC's another one, CGC, I'm going for the ones that I see on the ticker that go by every day. Canopy growth, medical marijuana, same thing as Cronus but it has already done its big pullback and has rallied once again. That went from the, also in the single digits all the way to the 59 area, pulls back to 25, runs to 52 and now it's at 40. So now I'm going to say to you, so now you're looking for an entry point or re-entry point, is that correct? Have Victor, oops, I think we just got cut off. Okay, so I'm sure that Victor's probably listening. So Cronus to me is in the area where it starts, it's in an area where it needs to find support. There is no support based on either the weekly or the monthly charts until a test of 1530s. So this is what I'm going to suggest to you and Victor, I know that you look at these quite intensely, but I'm going to say to you, I would put in a bid based on if you've already traded this and you've made money under those conditions, I would put a bid of a small position, I really do mean a small position, somewhere between $15.40 and $15.30, that's kind of the area that I'm looking at. The reason why I say that as a bid is because it's within 30, 40 cents of where we are right now. It's at a really sharp pullback. I don't see it on the weekly chart showing any strength whatsoever. I don't see it showing any strength in the daily and the monthly chart is still very strong technically because it has such a big move up and that's telling me that we could start the sideways choppy area so that there'll be moments where you're making profit on the trade and there are moments where you're going to be losing but it's a good feeler trade. It doesn't even have to be a lot of shares. You just wanna, you want to know how is this participating every day in the market when other areas are doing whatever they're doing? How does this particular stock in this particular group manage to hold support? And I'll explain why I'm saying that. The MJ is having a big move down at $24, 30, 385 right now and alternative harvest is the cannabis sector ETF. We were long, we've taken profits, we're actually out now. I'm looking at this and I'm saying that was our first big attempt at just getting into it. It wasn't a big position, but I'm saying our big attempt to start in an ETF that is really an IPO basically. There's no real history. Number one, number two is now I have a good feeling for taking profits because we had 30% profits. We didn't take 30%, we've taken quite a bit less but we have taken profits. I'm not prepared to give those profits up but rather get another trade in and for subscribers because this is an area that I think has legs to the upside in 2019 but I've got a feeling that it's overbought for other reasons. If you look at SDZ which is the constellation brands holding beautifully after the big move up two and a half weeks ago in the 190 area we're looking for some kind of a pullback into the 186, 185 area to go along with Greg's analysis that he did of the stock to say that that's where he'd like to get in. I said, you know what? You could do a little nibble here just to really see how it is because the way I'm looking at it I'm not sure it's just yet ready. Now, this is very important because constellation brand spirits beer and now it's got the cannabis segment as well as forgetting which one I want to look at it's SDZ and what's the other one? The big one. Oh, this is a GWPH. I remember symbols better than I do in names. GWPH stuck in the sideways range at 164, 69 down three. So I'm suspecting because these big ones ran up it's the opposite of what you look in sectors at major tops where the big guys take a rest and finally the little guys come running up and then they run out of gas and then everybody comes down. This is a little bit reversed and it's saying to me that there is interest in the bigger ones but I think the whole sector just needs a little more time to digest and so back to Victor. I'm not sure if he's still on if he can just say hi but sometimes people just have to go because they're either at work or they just don't stay online. They like to listen. They like, I think that's what you were saying to me in the background there. I'd like to listen and if you're doing that this is a big move for Cronus going from 24 down to 15 but look at it did that in two days on the way up and it's taken one, two, three, four, five, six, sorry, two weeks on the way up. It's taken one, two, three, four, five, six, seven broke the rectangle formation eight, nine this is the 10th week. I think there's a little more to go but this is an area you wanna keep your eye on. My subscribers know that we're keeping our eye on this as part of a portfolio but where you get in and how you keep I was just determined we're not gonna take a loss after having such a nice gain. We had to get out, we're out, took a 12% gain on one position we took another small position gain before. I'm just, I just don't want my subscribers to have something that did so well and then take a loss when you've been it's just not the way you wanted. Now we might miss the next entry I'll be planning for that in a certain way. Subscribers know just how I like to organize these things so let's hope that that's the way it's going to work out. Okay, hope I answered your question Victor it's a good question and the answer is if you're waiting to get in and I know you've been in this before I'm not sure how much money you made but if you have made money, have a little patience I would much rather let it find support and just to guess that this is the support and the next thing you know it goes right down to the 14 or the 13s it could do that the sector is vulnerable on the way up and look at the way it's vulnerable on the way down look at those big moves in the monthly just make a 50% or more sometimes even an 80% of the gain so I just don't want to be messing around with this but it is an area that I think has potential and I spoke about that with subscribers over the weekend when I did my studies of my various charts of what we're long and what we're looking for and what we want to be buying Okay, next question Oh, we've got one more segment to go I'm going to be on with Tommy O'Brien tomorrow at 10 let me just double check the new schedule because Tom's away I'll be on with Tommy at 10 tomorrow I'll be on with Tommy Wednesday at 10 and on Thursday to wrap up the week because a holiday Friday I'll be on at three, three to four to wrap up the week I'll be back straight after these messages in the nation for the S&P 500 for the last 12, 6 and 3 months Timer Digest also ranks me as the number one market timer for gold as well The fact is markets can be timed and I'll teach you the exact set of tools that I use that has transformed me into one of the best in what I do Sign up for Mastering Probability today by clicking on the newsletter tab on the homepage of TFNN.com and get immediate access to workshops where I take you step by step how to use an extraordinary set of tools as well as provide great market calls to Sign up today If you haven't checked out the newsletters page of TFNN.com what are you waiting for? All of the TFNN newsletters are informative, up-to-date, affordable and must have for every trader looking to gain a competitive informational edge in today's markets TFNN newsletters cover every aspect of the markets to offer you the very latest in market news plus new subscribers get to test drive our newsletters risk-free for 30 days from all aspects of the markets including stocks, bonds, metals, commodities and tech there's a newsletter to fit your needs exclusively from TFNN Stay informed each day you trade and get the competitive edge that will help you stay ahead of the game Visit our newsletters page by going to TFNN.com and click the newsletters button near the top of the page TFNN.com Educating investors You know what's cool? Taking something that's good for you something specifically formulated to help with weight loss better sleep, stress reduction and the need to detox Nicar, hunter and gatherer ancestors found all their nutritional requirements for health in their wild environment but today our food sources no longer contain the vitamins minerals and nutrients our bodies need to stay healthy and strong that's why we need primal edge daily nutrition it includes a special blend of ionics oil-based vitamins, minerals, fatty and amino acids in an easy to use liquid form primal edge is powered by highly concentrated folic and humic acids nature's preferred delivery system they've been called miracle molecules because like sunlight, air and water life cannot exist without them that's right Paige, they ensure we receive all the nutrition we need to be healthy and thrive we take it every morning primal edge, formulated and approved by Nico and Paige of living a primal lifestyle buy it today for just $89 click on the primal edge banner on the front page of TFNN.com Hi folks, this is Steve Rhodes stay tuned for another great hour of The Trader's Edge heard here at TFNN.com Hi everyone, we're back and we're looking at the two minute, five minute, 10 minute charts 10 minute gave a beautiful peak D right there in the two, 29, 13s we plummeted down to the 2900 level and bounced up to 2907 then back down to the 2902 now we're at 290450 make it real simple if at 310 between 310 and 317 if the E-mini is 10 to 11 points down or more that says that we're probably running into into Tuesday with this pullback and if there's a good rally and we can go over 2908 that's about four points higher and 2908 takes you down just about five-ish points, four points I would say that's good to have just a down but narrower down close as it took a breather today my thinking has been a little bit more time because that was a big move up on Friday T-O-R-Y mentioned in the den T-O-R-Y Inc. Medical Cannabis wonderful example of the Chapman Wave Eiffel Tower or A-Pattern remember the A-Pattern straight up, straight down the Duke Ellington A-Train this is what we've got right here was that Coltrane all right, next thing we're looking at is a single leg A-up to 300 round number high back to the 21st the week of the 21st of September of 2018 a little pullback to the 200-period moving average around about the 46s we're at 48, 85 right now what a move all right, that's what you've got to be careful of this is like treat this area a little like the biotechs 10 years ago or so if you looked at the charts you'll see that every few months it was a spectacular move and what they were doing is that they were paying their CEO or someone with their accountant one of the big people in the firm via stock purchases and the stock was going to soaring up and maybe that person sold took the money and you sold this every three months I mean, it was like clockwork all right, well, that's it you're going to have Steve Rhodes you're going to have Dave White and then who's on for the show this afternoon I think Larry Besaventa that should be one of Steve Rhodes and Dave White 3 o'clock to 4 p.m. have a wonderful day I'll see you tomorrow hey, check out my opening call hope you find it beneficial and profitable I'll be back tomorrow have a great day